reconfiguration of radio link monitoring / radio link failure by switching parts of bandwidth

专利摘要:
A method on a user equipment (UE) (110) is disclosed. The method comprises obtaining (701) one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth. The method comprises determining (702) that the UE should switch from a source bandwidth portion to a destination bandwidth portion. The method comprises performing (703) the radio link monitoring in the destination bandwidth part, according to a obtained radio link monitoring configuration associated with the destination bandwidth part.
公开号:BR112020009644A2
申请号:R112020009644-0
申请日:2018-11-14
公开日:2020-11-10
发明作者:Icaro L. J. Da Silva；Helka-Liina Määttanen；Iana Siomina；Muhammad Kazmi；Rui Fan
申请人:Telefonaktiebolaget Lm Ericsson (Publ)；
IPC主号:

专利说明:

[001] [001] The present invention relates, in general, to wireless communications and, more particularly, to provide optimizations for operating frequency of reduced transmission power control. BACKGROUND
[002] [002] In the treatment of Radio Link Monitoring (RLM) in Long Term Evolution (LTE), the main question is how the user equipment (UE) generates events In Sync (IS) and Out of Sync (OOS). An objective of the RLM function in the UE is to monitor the quality of the downlink radio link (DL) of the server cell in the RRC_CONNECTED state. It is based on Cell-Specific Reference Signals (CRS), which are associated with a given LTE cell and are derived from the Physical Cell Identifier (PCI). When in the RRC_CONNECTED state, this allows the UE to determine whether it is in sync or out of sync with its server cell.
[003] [003] The UE estimate of the quality of the DL radio link is compared to the limits of OOS and IS, (Qout and Qin respectively) for RLM purposes. These limits are expressed in terms of the Block Error Rate (BLER) of a hypothetical Physical Downlink Control Channel (PDCCH) transmission from the server cell. Specifically, Qout corresponds to a BLER of 10%, while Qin corresponds to a BLER of 2%. The same threshold levels are applicable with and without batch reception (XRD).
[004] [004] The mapping between the quality of DL based on CRS and the hypothetical PDCCH BLER depends on the implementation of UE. However, performance is verified by compliance tests defined for various environments. Additionally, the quality of DL is calculated based on the received power of reference signal (RSRP) from the CRS over the entire band, since the UE does not necessarily know where the PDCCH will be scaled. This is because the PDDCH can be scaled anywhere across the DL transmission bandwidth, as described in relation to FIGURE 1 below.
[005] [005] FIGURE 1 illustrates an example of how the PDCCH can be scaled over the entire DL transmission bandwidth. More particularly, Figure 1 illustrates a plurality of radio frames 10, each with a duration of 10ms. Each radio frame is made up of ten subframes 15, each subframe 15 lasting 1ms. The UE plays a sample per radio frame 10 for RLM. As noted above, the DL quality is calculated based on the CRS RSRP over the entire band, as the UE does not necessarily know where the PDCCH will be scheduled.
[006] [006] When no DRX is configured, OOS occurs when the quality of the DL radio link estimated in the last 200ms period becomes worse than the Qout limit. Similarly, without DRX, IS occurs when the quality of the DL radio link estimated in the last 100ms period becomes better than the Qin limit. Upon detection of OOS, the UE starts the evaluation of IS.
[007] [007] In Radio Link Failure (RLF) modeling in LTE, the main question is how the upper layers use the IS / OOS events generated internally from the RLM to control autonomous UE actions when it detects that it cannot be reached by the network while in RRC_CONNECTED. In LTE, occurrences of OOS and IS events are reported internally by the physical layer of the UE to its upper layers, which, in turn, can apply radio resource control (RRC) / layer 3 filtering
[008] [008] FIGURE 2 illustrates an exemplary procedure for evaluating LPR. In step 201, the UE detects a first OOS event. In step 203, the UE detects up to N310 consecutive events out of sync and starts the T310 timer (as described in the RRC 3GPP TS 38.331 specification, parts of which are extracted below). In step 205, timer T310 expires and RLF occurs. The UE transmitter is then switched off within 40ms, and the RRC reset procedure begins. The UE starts the T311 timer and the UE searches for the best cell. In step 207, the UE selects a target cell (that is, the best one). In step 209, the UE acquires system information (SI) for the destination cell and sends a random access channel (RACH) preamble to the destination cell. In step 211, the UE acquires an UL grant and sends an RRC connection re-request message.
[009] [009] As noted above, the detailed EU actions that concern RFL are captured in the RRC specifications (3GPP TS 38.331). A part of 3GPP TS 38.331 is extracted below:
[010] [010] The RLF-TimersAndConstants information element (IE) contains UE-specific timers and constants applicable to UEs in RRC_CONNECTED. Shown below is an abstract syntax notation (ASN.1) for RLF-TimersAndConstants IE. - ASN1START RLF-TimersAndConstants-r9 :: = CHOICE {release NULL, setup SEQUENCE {t301-r9 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000},
[011] [011] Table 1 below provides field descriptions for the RLF- TimersAndConstants IE. Table 1 Field Descriptions of RLF-TimersAndConstants n3xy The constants are described in section 7.4. n1 corresponds to 1, n2 corresponds to 2, and so on. t3xy Timers are described in section 7.3. The ms0 value corresponds to 0 ms, ms50 corresponds to 50 ms and so on. E-UTRAN configures RLF-TimersAndConstants-r13 only if the UE supports ce-ModeB. The UE should use the extended values t3xy-v1310 and t3xy-v1330, if present, and ignore the values signaled by t3xy-r9.
[012] [012] Additional information on timers and constants is provided in Tables 2 and 3 below, respectively. Table 2: Timers
[013] [013] When XRD is in use, the OOS and IS evaluation periods are extended to allow sufficient EU power savings. In such a scenario, the length of the OOS and IS evaluation periods depends on the configured XRD cycle length. The UE starts the evaluation of IS whenever OOS occurs. Therefore, the same period (TEvaluate_Qout_DRX) is used for the evaluation of OOS and IS. However, by starting the sleep timer
[014] [014] The entire methodology used for RLM in LTE (ie measuring the CRS to "estimate" the quality of the PDCCH) depends on the fact that the UE is connected to an LTE cell, which is the only connectivity entity which transmits PDCCH and CRSs.
[015] [015] In summary, the RLM in LTE has been specified so that the network does not need to configure any parameters (that is, the UE generates IS / OOS events internally from the lowest to the highest layers to control problem detection on the radio link). On the other hand, the RLF / Secondary Cell Group (SCG) failure procedures are controlled by RRC and configured by the network via counters (for example, N310, N311, N313, N314 (which work as filters to prevent early triggering of RLF) and timers (for example, T310, T311, T313 and T314).
[016] [016] The RLF parameters are configured in the IEs rlf- TimersAndConstants or radioResourceConfigDedicated IE. The rlf- TimersAndConstants IE can be transmitted in SystemInformationBlockType2 (or SystemInformationBlockType2-NB in Narrow Bandwidth Internet of Things (NB-IoT)). RadioResourceConfigDedicated IE can be within RRC messages, such as RRCConnectionReconfiguration, RRCConnectionReestablishment or RRCConnectionResume, and RRCConnectionSetup.
[017] [017] The SCG Failure parameters are configured in the IEs rlf- TimersAndConstantsSCG, which can be transmitted in RadioResourceConfigDedicatedSCG-r12IE The RadioResourceConfigDedicatedSCG-
[018] [018] In Novo Rádio (NR), RLM is also defined for a purpose similar to that of LTE, that is, it monitors the quality of the DL radio link of the server cell in the RRC_CONNECTED state. However, unlike LTE, some level of configurability for RLM was introduced in NR in terms of configuration of RLM resource / beam / reference signal type (RS) and BLER limits for IS / OOS generation.
[019] [019] Regarding the configuration of the RS / beam / RLM type resource, in NR two RS types are defined for the mobility of L3: Physical Diffusion Channel (PBCH) / Synchronization Signal Block (SS) (Block of SSB or SS); and Channel State Information Reference Signal (CSI-RS). The SSB basically comprises synchronization signals equivalent to the Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) in LTE and PBCH / Demodulation Reference Signals (DMRS). CSI-RS for L3 mobility is more configurable and configured via dedicated signaling. There are different reasons for defining the two types of RS, one being the possibility of transmitting SSBs in wide beams and transmitting CSI-RSs in narrow beams.
[020] [020] In RAN1 # NR AdHoc # 2, it was agreed that in NR the type of RS used for RLM is also configurable (RLM based on CSI-RS and RLM based on SSB supported. It seems natural that the type of RS for RLM should be configured via RRC signaling In RAN1 # 90, it was agreed to support the unique type of RLM-RS only for different RLM-RS resources for one UE at a time.
[021] [021] Since NR can operate at very high frequencies (above 6 GHz, but up to 100 GHz), these types of RS used for RLM can be formed by beam. That is, depending on the frequency of implantation or operation, the UE can be configured to monitor reference signals generated by beam, regardless of which type of RS is selected for RLM. Therefore,
[022] [022] In the case of CSI-RS, the time / frequency feature and the sequence can be used. Since there may be multiple beams, the UE needs to know which ones to monitor for the RLM and how to generate IS / OOS events. In the case of SSB, each beam can be identified by an SSB index (derived from a PBCH time index and / or a PBCH / DMRS scramble). In RAN1 # 90, it was agreed that this is configurable and, in NR, the network can configure by RRC signaling, X RLM resources, related to SS or CSI-RS blocks. An RLM-RS resource can be a PBCHSS block or a CSI-RS resource / port. The RLM-RS features are configured specifically for UE at least in the case of RLM based on CSI-RS. When the UE is configured to perform RLM on one or multiple RLM-RS resource (s): periodic IS is indicated if the estimated link quality corresponding to the hypothetical PDCCH BLER based on at least Y resource (s) RLM-RS among all the X RLM-RS resource (s) configured are above the Q_in limit; and periodic OOS is indicated if the estimated link quality corresponding to the hypothetical PDCCH BLER based on all configured X RLM-RS resources is below the Q_out limit. There may also be a change in the number of RLM resources.
[023] [023] Regarding the IS / OOS and BLER threshold configuration, the UE needs to know which resources to monitor, as well as generate IS / OOS events to be reported internally in upper layers. Regarding the generation of IS / OOS indication (s), in RAN1 # 89 and RAN1 # 90, it was agreed that RAN1 plans to provide at least periodic IS / OOS indications and the hypothetical PDCCH BLER is used as a metric to determine conditions from IS / OOS to RLM based on PBCH / SS block and based on CSI-RS.
[024] [024] Unlike LTE, in which the signal-interference-plus-
[025] [025] While the functionality of RLM had significant changes in NR (that is, a more configurable procedure was defined in which the network can define the type of RS, exact resources to be monitored and even the BLER for indications of IS and OOS), the RLF did not show major changes in NR compared to LTE. In RAN2 # 99-bis in Prague, it was agreed that (1) the detection of RLF will be specified for NR in the RRC specification (as in LTE) and (2) for December 17, the RLF will be based on the indications of IS / Periodic OOS of L1 (ie, this is the same table as LTE). In addition, it was agreed that for connected mode, the UE declares RLF upon expiration of the timer due to DL OOS detection, random access procedure failure detection and RLC failure detection. It is for additional study (FFS) if the Automatic Retry Request (ARQ) retransmission is the only criterion for radio link control failure (RLC). It was also agreed that in NR RLM procedures, the physical layer performs an OOS / IS indication and the RRC declares RLF. It was also agreed that for RLF purposes, the preference for RAN2 is that the indication IS / OOS should be an indication per cell, with the objective of a single procedure for multibeam and single beam operation.
[026] [026] At RAN # 99 in Berlin, it was further agreed that RAN2's understanding of RAN1 agreements that at least the physical layer informs the RRC of periodic OOS / IS indications, and that the baseline behavior when there are no indications of lower layers related to beam failure / recovery is that (1) the RRC detects a DL radio link problem if the consecutive N1 number of periodic OOS indications is received and (2) the RRC for the timer if the consecutive N2 number periodic IS indications is received while the timer is running. In other words, as in LTE, it is possible to assume that RLF in NR will also be governed by the following parameter or equivalents: counters N310, N311, N313, N314; and timers 310, T311, T301, T313, T314.
[027] [027] It is reproduced below how the RLF variables can be configured in the behavior of NR and UE as recently agreed for NR.
[028] [028] Additional information about the timers and constants can be configured in NR are provided in Tables 4 and 5 below, respectively. Table 4: Timers Time Start Stop On expiration rizer T307 Successful Completion Reception Inform E- message of random access in the UTRAN / NR about the RRCConnectionRe PSCell, upon the beginning of the failure to change the SCG configuration and when starting including by MobilityControlInf SCG procedure release information about SCG SCG failures as specified in
[029] [029] As noted above, the RLF-TimersAndConstants of IE contains UE-specific timers and constants applicable to the UEs in RRC_CONNECTED. An example of how ANS.1 for RLF- TimersAndConstants IE can appear in NR is shown below.
[030] [030] RAN1 introduced the concept of parts of bandwidth (BWP), which intends to configure the UE with an operating bandwidth that may be less than the actual carrier bandwidth. This has similarities with the handling of "low bandwidth" UEs in LTE (Cat-M1), which are not able to operate with the full carrier bandwidth. Note that this description is mainly about carriers that span several 100 MHz and UEs supporting, for example, “only” 100 MHz carriers. That is, this concept addresses UEs that support an operational bandwidth that is 100 times wider than for Cat-M1. Similar to LTE Cat-M1, the configured BWP may not match the carrier SSB (PSS / SSS / PBCH / Master Information Block (MIB)) and it must be determined how the UE acquires cellular synchronization, performs measurements and acquires system information (SIB) in these cases. In addition to this core part of BWP functionality, RAN1 also discussed other variations (for example, with additional SSBs on the same carrier or the same BWP, as well as the possibility of configuring a UE with several possibly overlapping BWPs, among which the network can switch via L1 control signals (for example, downlink control (DCI) information).
[031] [031] FIGURE 3 illustrates an example of parts of bandwidth. More particularly, FIGURE 3 illustrates the bandwidth of a single wide component carrier 300 made up of a number of physical resource blocks (PRBs) 1 through N. In the example of FIGURE 3, three BWPs are shown, BWPs 305A, 305B and 305C. BWP 305A is a first part of bandwidth for a first UE, UE 1. BWP 305A is a first part of bandwidth for a second UE, UE2. The BWP 305C is a second piece of bandwidth for the second UE, the UE2. BWP 305A for UE1 corresponds to the maximum bandwidth of UE1, while BWP 305C corresponds to the maximum bandwidth of UE2.
[032] [032] DL and UL BWPs determine the frequency range in which the UE should receive and transmit data channels (for example, Physical DL Shared Channel (PDSCH) and Physical UL Shared Channel (PUSCH)) and channels corresponding control units (PDCCH and Physical UL Control Channel (PUCCH)). As a starting point, a BWP cannot cover more than the configured carrier bandwidth. Thus, a BWP is less than or equal to (but not greater than) than the carrier bandwidth.
[033] [033] A major aspect of the BWP concept (as opposed to using only carrier bandwidth) is to support UEs that cannot handle all carrier bandwidth. UEs that support the full carrier bandwidth can also use the entire carrier. Therefore, the network is expected to configure DL BWP and UL BWP in dedicated signaling according to EU capabilities.
[034] [034] For example, BWPs can be configured by dedicated signaling in the first RRCConnectionReconfiguration after the connection is established (that is, when the network knows the capabilities of the UE). Before that time, however, the UE must read the PDCCH and PDSCH to acquire SIB1 to receive radiolocation messages and to receive Msg2, Msg4 (from the random access procedures) and the RRCConnectionReconfiguration described above. Therefore, the UE must be configured with an "initial BWP". In RAN 1, it was agreed that there is an initial active DL / UL BWP pair that is valid for a UE until the UE is explicitly configured (or reconfigured) with BWP (s) during or after the RRC connection is established. It was further agreed that the portion of the initial active DL / UL bandwidth is confined within the minimum bandwidth of the UE for the specified frequency band. The details of the initial active DL / UL BWP are for further study.
[035] [035] In some cases, a network may decide to configure an initial BWP wider than some UEs support. This may be the case, for example, if the network wants to optimize the acquisition time or the SIB connection establishment time when using a wider bandwidth. But this situation can also occur if a legacy network does not yet support less complex UEs. The UE finds this out based on the initial BWP configured in MIB and, since it cannot acquire SIB1, it must consider the cell as blocked.
[036] [036] Upon successful connection establishment, the network must configure a BWP according to the capabilities of the UE. The BWP configuration is specific to a server cell (that is, the network must configure at least one DL BWP for each server cell). The UL BWP is configured for Primary Cells (PCells) and for Secondary Cells (Scells) with the UL configured.
[037] [037] FIGURE 4 illustrates an example of parts of standard bandwidth. More particularly, FIGURE 4 illustrates the bandwidth of a single broad component carrier 400 made from a number of PRBs 1 through N.
[038] [038] In LTE, each cell was characterized by its central frequency (UL + DL for Frequency Division Duplexing (FDD)), the carrier bandwidth and the PCI transported in PSS / SSS. The PSS / SSS used to be at the carrier's central frequency. In NR, however, the SSB frequency is not necessarily the central frequency, which requires signaling values or a value and offset (as already discussed in the context of Radio Resource Management (RRM) measurements). Upon initial access, the UE must discover the (one) SSB, acquire synchronization, acquire MIB and then try to read the SIB1. At that point, the UE selected the cell (that is, an SSB at a certain frequency).
[039] [039] When the UE establishes an RRC connection, the network can configure a dedicated BWP. This BWP can override the SSB frequency. If this happens, the UE will be able to acquire (or reacquire) the SSB at any time in order to regain synchronization and perform measurements based on SS. If the UE BWP DL matches the SSB frequency of the UE server cell, the UE does not require inter-frequency measurement gaps to acquire (or reacquire) the SSB and to perform SS-based measurements.
[040] [040] If a cell (carrier) bandwidth operation is wide and if multiple UEs have an operational bandwidth that is significantly narrower than the carrier bandwidth, however, the network will allocate UEs for BWPs that do not match the SSB frequency in order to balance the load and to maximize the capacity of the system, such a scenario is illustrated in figure 4, where the BWP 405A and 405C does not match the SSB on the component carrier 400. As in LTE Cat-M1, this implies that these UEs need measurement gaps (inter-frequency, intraport) to resynchronize with their server cell SSB and to detect and measure neighboring cells. In other words, if the UE's DL BWP does not match the SSB frequency of the UE service cell, the UE requires inter-frequency (intraport) measurement gaps to acquire (or reacquire) the SSB and to perform SS-based measurements.
[041] [041] This is a natural consequence of the decision to deploy a cell with broad operational bandwidth with only a single SSB and a single occurrence of System Information. However, RAN1 suggests introducing the possibility of informing an UE about additional SSB frequencies within a carrier and thereby ensuring that each / more UE finds an SSB in its configured BWP. At first glance, this can remove the need for measurement gaps. However, this does not fit with how RAN2 has defined RRM measurements. In most RRM measurement events, the UE compares a cell next to the server cell. As explained above, a cell is characterized by an SSB at a certain frequency and the associated SIB1. The UE selects such a cell (initial access) or is configured with that server cell (for example, during the addition of a handover SCell (HO). This seems to suggest that a UE being configured with a BWP containing its own SSB should be moved to that cell (that is, the UE must make an HO of interference from its SSB from the original cell to the BWP SSB). If that SSB is also associated with the system information (at least SIB1), the UE can camp on that SSB, which is actually just another cell, so configuring a UE with a BWP and an SSB within that BWP is equivalent to inter-frequency HO if that SSB is associated with at least SIB1.
[042] [042] This ensures that all RRM measurement settings remain unchanged (that is, the UE simply considers the new SSB as its serving cell and searches (typically) for neighboring cell SSBs at the same frequency).
[043] [043] A change in BWP will typically require readjusting the radio frequency (RF) of the UE. Such RL readjustment occurs, for example, by activating / deactivating SCell in LTE. Based on the assessment of RAN4, it caused at least interruptions (for example, errors) in the order of a subframe. Activating a new carrier takes up to ~ 30ms. RAN4 has not investigated how long it can take to switch between BWPs. It can depend on whether BWPs use the same SSB as a synchronization reference and whether a BWP is just a subset of another BWP or not. RAN1 discussed the possibility of configuring several BWPs that possibly overlap via RRC and thus switch more dynamically through L1 control signaling.
[044] [044] The topic of BWP and multi-SSB by carrier was discussed in RAN2 # 99-bis and the following agreements were made for the operation of BWP in CONNECTED mode. RRC signaling supports configuring one or more BWPs (both for DL BWP and UL BWP) for a server cell (PCell, PSCell). RRC signaling supports configuring 0, 1 or more BWPs (both for DL BWP and UL BWP) for a SCell server cell (at least 1 DL BWP). For a UE, PCell, PSCell and each Scell have a single SSB associated in frequency (the terminology of RAN1 is the “cell defining SSB”) The cell defining the SS block can be changed by synchronous reconfiguration for release / add PCell / PSCell for SCell. Each SS block frequency that needs to be measured by the UE must be configured as an individual measurement object (that is, a measurement object corresponds to a single SS block frequency). The cell that defines the SS block is considered as the time reference of the server cell and for RRM server cell measurements based on SSB (regardless of which BWP is enabled). It is for future study if additional optimization is needed to change the location of the SS block in the frequency (but without any change to PCI and no change in the system frame number (SFN)) to be changed by the RRC reconfiguration of parameters of physical layer with no L2 involvement.
[045] [045] Considering that the RLM can be performed when configuring PBCH / SS blocks or CSI-RS resources, and that for a given cell there will be only one PBCH / SS block and that may not fall within the active BWP, there are some problems for configuring RLM in the context of BWPs. The main problem is that when changing the BWP (for example, using L1 signaling or depending on a time-based solution where the UE must switch from one BWP to another BWP when the timer expires), the UE may require using gaps measurement to perform RRM measurements even for the server cell in case they are configured to be based on PBCH / SS blocks and the PBCH / SS block for the server cell is not within the active BWP for which the UE is being switched. In addition, changing the BWP can lead to changes in the RLM resources that the UE monitors, especially if the PDCCH configuration also changes. In addition, there may be a need to change the type of RS that the UE monitors, as the target active BWP may not include the type / features of the RS that the UE was monitoring in the previous active BWP. There may also be a change in the number of RLM resources. SUMMARY
[046] [046] To address previous problems with existing solutions, a method in a UE is disclosed. The method comprises obtaining one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth. The method comprises determining that the UE should switch from a source bandwidth portion to a destination bandwidth portion. The method comprises performing the radio link monitoring in the destination bandwidth part, according to a obtained radio link monitoring configuration associated with the destination bandwidth part.
[047] [047] In certain modalities, obtaining one or more radio link monitoring configurations comprises receiving one or more radio link monitoring configurations in a message from a network node. In certain embodiments, in obtaining one or more radio link monitoring configurations you can understand determining one or more radio link monitoring configurations according to one or more predefined rules.
[048] [048] In certain embodiments, each radio link monitoring configuration may comprise: a set of radio resources to perform radio link monitoring within its associated bandwidth portion; and one or more configuration parameters to perform radio link monitoring within its associated bandwidth portion.
[049] [049] In certain embodiments, the radio resource set may comprise a CSI-RS resource. In certain embodiments, the radio resource set may comprise an SSB.
[050] [050] In certain embodiments, the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion may comprise one or more of: one or more filtering parameters; one or more radio link failure timers; an evaluation period; a number of retransmissions before the radio link failure is declared; a hypothetical channel configuration; a hypothetical signal configuration; and a mapping function for a measured link quality and a hypothetical channel block error rate. In certain embodiments, the one or more configuration parameters for performing radio link monitoring within their associated bandwidth portion may comprise one or more filter parameters and the one or more filter parameters may comprise one or more of the counters. N310, N311 and N313, N314. In certain embodiments, the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion may comprise one or more radio link failure timers and one or more radio link failure timers. radio may comprise one or more of the T310, T311, T313 and T314 timers.
[051] [051] In certain embodiments, in at least one of the one or more radio link monitoring configurations obtained may comprise a standard radio link monitoring configuration. In certain embodiments, the standard radio link monitoring configuration may be associated with the standard bandwidth portion.
[052] [052] In certain embodiments, the method may comprise monitoring a downlink channel quality of a first part of bandwidth and a second part of bandwidth. In certain embodiments, performance monitoring may comprise: estimating, during a first period of time, a radio link quality of the first part of bandwidth according to a radio link monitoring configuration associated with the first part of bandwidth; and estimating, over a second period of time, a radio link quality of the second part of bandwidth according to a radio link monitoring configuration associated with the second part of bandwidth, in which the second period is time overlaps with the first period of time at least partially. In certain embodiments, a first part of the bandwidth may comprise the source bandwidth part and the second bandwidth part may comprise the destination bandwidth part. In certain embodiments, monitoring can be triggered based on an activation rate of one or more of the first part of bandwidth and the second part of bandwidth.
[053] [053] In certain embodiments, the radio link monitoring configuration associated with the destination bandwidth portion may comprise a plurality of sets of radio resources and the method may further comprise selecting one or more from the plurality of sets of radio resources to be used to perform radio link monitoring in the destination bandwidth portion based on a predefined rule.
[054] [054] In certain embodiments, a plurality of radio link monitoring configurations may be associated with the destination bandwidth portion, and the method may additionally comprise receiving an instruction via downlink control information to use one of the plurality of radio link monitoring configurations to perform radio link monitoring in the destination bandwidth portion.
[055] [055] In certain embodiments, a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion may use the same radio resources and performing radio link monitoring on the target bandwidth portion according to the radio link monitoring configuration obtained associated with the destination bandwidth portion may comprise using one or more of the measurements performed previously and measurement samples performed previously to generate events out of sync and in sync.
[056] [056] In certain embodiments, a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion may use different radio resources. In certain embodiments, performing radio link monitoring on the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion may comprise applying a relationship function to one or more of the measurements previously performed and samples of measurements previously performed to generate events out of sync and in sync without resetting a radio link failure timer or radio link failure counter. In certain embodiments, performing radio link monitoring on the destination bandwidth portion according to the radio link monitoring configuration obtained associated with the destination bandwidth portion may comprise restarting at least one link failure timer radio link and a radio link failure counter. In certain embodiments, resetting at least one of a radio link failure timer and a radio link failure counter may comprise resetting a set of radio link failure timers and radio link failure counters associated with monitoring link errors for out of sync events and allow a set of radio link failure timers and radio link failure counters associated with radio link monitoring for sync events to continue. In certain embodiments, resetting at least one of a radio link failure timer and a radio link failure counter may comprise resetting one or more radio link failure timers without resetting any of the radio link failure counters .
[057] [057] An UE is also released. The UE comprises a receiver, a transmitter and a set of processing circuits coupled to the receiver and the transmitter. The processing circuitry is configured to obtain one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth. The processing circuitry is configured to determine that the UE should switch from a source bandwidth portion to a destination bandwidth portion. The processing circuitry is configured to perform radio link monitoring on the destination bandwidth portion, according to a obtained radio link monitoring configuration associated with the destination bandwidth portion.
[058] [058] A computer program is also disclosed, the computer program comprising instructions configured to perform the method described above on a UE.
[059] [059] A computer program product is also disclosed, the computer program product comprising a non-transitory computer-readable storage medium, a non-transitory computer-readable storage medium comprising a computer program comprising computer executable instructions that , when run on a processor, are configured to perform the method described above on a UE.
[060] [060] A method on a network node is also disclosed. The method comprises determining one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth. The method comprises configuring a UE to perform radio link monitoring on a destination bandwidth portion according to a radio link monitoring configuration associated with the destination bandwidth portion.
[061] [061] In certain embodiments, configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion may comprise sending an indication the radio link monitoring configuration associated with the destination bandwidth portion for the UE. In certain embodiments, sending the indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE may comprise sending an indication of the radio link monitoring configuration associated with the destination bandwidth portion in an information element within a bandwidth portion setting for the destination bandwidth portion. In certain embodiments, sending the indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE may comprise sending an indication of the radio link monitoring configuration associated with the destination bandwidth portion in an information element within a server cell configuration. In certain embodiments, the indication may comprise a radio link monitoring configuration identifier.
[062] [062] In certain embodiments, configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion may comprise configuring the UE to determine radio link monitoring configuration associated with the destination bandwidth portion according to one or more predefined rules.
[063] [063] In certain embodiments, each radio link monitoring configuration may comprise a set of radio resources to perform radio link monitoring within its associated bandwidth portion and one or more configuration parameters to perform radio monitoring. radio link within its associated bandwidth portion. In certain embodiments, the radio resource set may comprise a CSI-RS resource. In certain embodiments, the radio resource set may comprise an SSB.
[064] [064] In certain embodiments, the one or more configuration parameters for performing radio link monitoring within their associated bandwidth portion comprise one or more of: one or more filtering parameters; one or more radio link failure timers; an evaluation period; a number of retransmissions before the radio link failure is declared; a hypothetical channel configuration; a hypothetical signal configuration; and a mapping function for a measured link quality and a hypothetical channel block error rate. In certain embodiments, the one or more configuration parameters for performing radio link monitoring within their associated bandwidth portion may comprise one or more filter parameters and the one or more filter parameters may comprise one or more of the counters. N310, N311 and N313, N314. In certain embodiments, the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion may comprise one or more radio link failure timers and one or more radio link failure timers. radio may comprise one or more of the T310, T311, T313 and T314 timers.
[065] [065] In certain embodiments, in at least one or more of the determined radio link monitoring configurations may comprise a standard radio link monitoring configuration. In certain embodiments, the standard radio link monitoring configuration may be associated with the standard bandwidth portion.
[066] [066] In certain embodiments, the radio link monitoring configuration associated with the destination bandwidth portion may comprise a plurality of sets of radio resources and the method may further comprise configuring the UE to select one or more among the plurality of sets of radio resources to be used to perform radio link monitoring in the destination bandwidth portion based on a predefined rule.
[067] [067] In certain embodiments, a plurality of radio link monitoring configurations may be associated with the destination bandwidth portion, and the method may further comprise sending an instruction to the UE to use one of the plurality of radio link monitoring configurations to perform radio link monitoring in the destination bandwidth portion.
[068] [068] In certain embodiments, a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with a destination bandwidth portion may use the same radio resources and configuring the UE to perform radio link monitoring on the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion may comprise configuring the UE to use one or more of the measurements performed previously and measurement samples performed previously to generate events out of sync and in sync.
[069] [069] In certain embodiments, a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with a destination bandwidth portion use different radio resources. In certain embodiments, configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion may comprise configuring the UE to apply a function of relation to one or more of the measurements previously performed and samples of measurements previously performed to generate events out of sync and in sync without resetting a radio link failure timer or a radio link failure counter. In certain embodiments, configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the obtained radio link monitoring configuration associated with the destination bandwidth portion may comprise configuring the UE to reset at least one of a radio link failure timer and a radio link failure counter. In certain embodiments, configuring the UE to reset at least one of a radio link failure timer and a radio link failure counter may comprise configuring the UE to reset a set of radio link failure timers and radio counters. radio link failure associated with radio link monitoring for out of sync events and configure the UE to allow a set of radio link failure timers and radio link failure counters associated with radio link monitoring to synchronized events continue. In certain embodiments, configuring the UE to reset at least one of a radio link failure timer and a radio link failure counter may comprise configuring the UE to reset one or more radio link failure timers without restarting any radio link failure counters.
[070] [070] A network node is also disclosed. The network node comprises a receiver, a transmitter and a set of processing circuits coupled to the receiver and the transmitter. The processing circuitry is configured to determine one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth. The processing circuitry is configured to configure a UE to perform radio link monitoring on a destination bandwidth portion according to a radio link monitoring configuration associated with the destination bandwidth portion.
[071] [071] A computer program is also disclosed, the computer program comprising instructions configured to perform the method described above on a network node.
[072] [072] A computer program product is also disclosed, the computer program product comprising a non-transitory computer-readable storage medium, a non-transitory computer-readable storage medium comprising a computer program comprising computer executable instructions that , when run on a processor, are configured to perform the method described above on a network node.
[073] [073] Certain modalities of the present description may provide one or more technical advantages. For example, certain modalities can advantageously allow an efficient change in the configuration of the radio link failure / radio link monitoring when the UE sets the bandwidth part. This can advantageously allow you to avoid frequent measurement gaps without excessive additional signaling. Other advantages may be readily apparent to those skilled in the art. Certain modalities may not have any, some or all of the advantages mentioned. BRIEF DESCRIPTION OF THE FIGURES
[074] [074] For a more complete understanding of the disclosed modalities and their characteristics and advantages, reference will now be made to the description below, taken in conjunction with the attached drawings, in which: FIGURE 1 illustrates an example of how the PDCCH can be staggered over the entire DL transmission bandwidth; FIGURE 2 illustrates a procedure for evaluating exemplary FRL; FIGURE 3 illustrates an example of parts of bandwidth; FIGURE 4 illustrates an example of parts of standard bandwidth; FIGURES 5A and 5B illustrate a broadband component carrier with a single SSB frequency location and multiple parts of bandwidth; FIGURE 6 illustrates an exemplary wireless communications network according to certain modalities; FIGURE 7 is a flow chart of a method in an UE according to certain modalities;
[075] [075] In general, all terms used in the present invention must be interpreted according to their common meaning in the relevant technical field,
[076] [076] As described above, in NR the RLM can be performed when configuring PBCH / SS blocks or CSI-RS resources and for a given cell there will be only one PBCH / SS block (which may not fall within the active BWP ). As a result, there are certain problems with the configuration of RLM that can occur in the context of BWPs. For example, when changing the BWP, the UE may need to use measurement gaps to perform RRM measurements even for the serving cell in cases where RRM measurements are configured to be based on PBCH / SS Blocks and the PBCH / Block SS for the server cell is not within the active BWP to which the UE is switching.
[077] [077] For RRM measurements in the server cell, measurement gaps can be used as in LTE Cat-M1 UEs. RLM measurements used to compute the SINR (then map to a Qout / Qin threshold relative to a BLER mapped so that IS / OOS events can be generated), however, must be performed much more frequently than RRM measurements ( in LTE, on the order of 4 times more often). In other words, while RRM measurements are typically performed every 40ms, RLM measurements are performed per radio frame (that is, every 10ms). This could mean using extremely frequent measurement gaps (for example, in configurations where the type and / or frequency resources of RS to be monitored by RLM are outside the active BWP), which is not feasible. The impact that replacement of the PBCH / SS Block can have on the need for measurement gaps as illustrated in FIGURES 5A and 5B, which are described in more detail below.
[078] [078] FIGURES 5A and 5B illustrate a broadband component carrier with a single SSB frequency location and multiple BWPs. In FIGURE 5A, three BWPs 505A, 505B and 505C are illustrated. In addition, there is a single SSB 510A. As can be seen in FIGURE 5A, SSB 510A falls between each of the BWPs 505A, 505B and 505C. Therefore, when switching between BWPs 505A, 505B and 505C (for example, via L1 signaling), there is no need to reconfigure RRM measurements when switching BWPs. Therefore, there is no need for gaps in the scenario illustrated in FIGURE 5A.
[079] [079] Meanwhile, FIGURE 5B illustrates three BWPs 505D, 505E and 505F. FIGURE 5B also depicts a single SSB 510B. In contrast to the scenario illustrated in FIGURE 5A, in FIGURE 5B only one of the BWPs, the BWP 505E, includes SSB 510B. Therefore, when switching between BWPs (for example via L1 signaling), if the active BWP is reconfigured to be BWP 505D or BWP 505F, a UE may need gaps (ie reconfiguration via BWP switching is required or at least the UE must start using previously configured gaps (activating a previously configured gap)). For RLM, this can occur very often and may not be very efficient, especially if SSB 510B is used for RLM.
[080] [080] In addition to needing to use measurement gaps to perform RRM measurements as described above, there are other problems with the configuration of RLM that can occur in the context of BWPs. As an additional example, changing the BWP can lead to changes in the RLM resources that the UE monitors (especially if the PDCCH configuration also changes). As another example, there may be a need to change the type of RS that the UE monitors, as the target active BWP may not include the type / RS resources that the UE was monitoring in the previous active BWP. As yet another example, there may also be a change in the number of RLM resources.
[081] [081] A possible alternative could be relying on RRC signaling (for example, RRC Connection Reconfiguration) for scenarios in which the target BWP becomes active do not include the features that the UE was monitoring for RLM purposes in the BWP of source. This could mean, however, that every time there is a change from a source BWP to a destination BWP (done via L1 signaling or based on what the RAN1 timer agreed) RRC signaling will be required. This defeats the purpose of signaling optimization for BWP switching.
[082] [082] Additionally, the relationship (and therefore the mapping) between a measured channel quality (eg SINR) and the hypothetical BLER control channel may be different depending on the BWP. In addition, an old BWP can contain SS Blocks and thus the SS Block-based RLM can be configured, while a new BWP may not contain SS Blocks and therefore the CSI-RS-based RLM (where CSI-RS contained within the new BWP) may be more useful.
[083] [083] Certain aspects of the present description and the modalities described in the present invention can provide solutions to these or other challenges. According to another exemplary embodiment, a method is disclosed on a wireless device (WD) (for example, a UE). WD obtains one or more RLM configurations, each RLM configuration associated with at least one BWP. In certain embodiments, the WD 110 can obtain one or more RLM configurations when receiving one or more RLM configurations in a message from a network node (for example, a gNB). In certain embodiments, WD can obtain one or more RLM configurations by determining one or more RLM configurations according to one or more predefined rules. In certain embodiments, each RLM configuration may comprise a set of radio resources to perform RLM within its associated BWP and one or more configuration parameters to perform RLM within its associated bandwidth portion. The WD determines that the WD must switch from a source BWP to a destination BWP. The WD performs RLM on the target BWP according to an obtained RLM configuration associated with the target BWP.
[084] [084] According to another exemplary modality, a method is disclosed on a network node (for example, a gNB). The network node determines one or more RLM configurations, each RLM configuration associated with at least one BWP. The network node configures a WD to perform RLM on a target BWP according to an RLM configuration associated with the target BWP. In certain embodiments, the network node can send an RLM configuration indication associated with the target BWP to the WD (for example, in one in an IE within a BWP configuration to the target BWP and / or in an IE within a server cell configuration). In certain embodiments, the indication may comprise an RLM configuration identifier.
[085] [085] Some of the modalities contemplated in the present invention will now be described more fully with reference to the accompanying drawings. Other modalities, however, are contained within the scope of the matter disclosed in the present invention, the disclosed matter should not be construed as limited to only the modalities established in the present invention; instead, these modalities are provided as an example to convey the scope of the matter to the technicians in the subject.
[086] [086] FIGURE 6 illustrates an exemplary wireless communications network in accordance with certain modalities. Although the subject described in the present invention can be implemented in any suitable type of system using any suitable components, the modalities disclosed in the present invention are described in relation to a wireless network, such as the exemplary wireless network illustrated in FIGURE 6. To simplify , the wireless network of FIGURE 6 represents only network 106, network nodes 160 and 160b and wireless devices (WDs) 110, 110b and 110c. In practice, the wireless network may additionally include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline, a service provider or any other network node or final device. Among the components illustrated, network node 160 and WD 110 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices' access to and / or use of services provided by, or via, the wireless network.
[087] [087] The wireless network can comprise and / or interface with any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, the wireless network can be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular modalities of the wireless network may implement communication standards, such as the Global Mobile Communications System (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE) and / or other standards of 2G, 3G, Suitable 4G or 5G; wireless local area network (WLAN) standards, such as IEEE 802.11 standards; and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability Standards for Microwave Access (WiMax), Bluetooth, Z-Wave and / or ZigBee.
[088] [088] Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, geographically distributed networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to allow communication between devices.
[089] [089] Network node 160 and WD 110 comprise several components described in more detail below. These components work together to provide the network node and / or wireless device functionality, such as providing wireless connections on a wireless network. In different modalities, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations and / or any other components or systems that can facilitate or participate in communication data and / or signals via wired or wireless connections.
[090] [090] As used in the present invention, a network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other nodes or network equipment on the wireless network to enable and / or provide wireless access to the wireless device and / or to perform other functions (for example, administration) on the wireless network.
[091] [091] In FIGURE 6, network node 160 includes a set of processing circuits 170, medium readable by device 180, interface 190, auxiliary equipment 184, power source 186, power circuit 187 and antenna 162. Although the node network 160 illustrated in the exemplary wireless network of FIGURE 6 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and / or software necessary to perform the tasks, characteristics, functions and methods disclosed in the present invention. In addition, while components of network node 160 are depicted as single boxes located within a larger box or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (for example, example, device-readable medium 180 may comprise multiple separate hard drives, as well as multiple RAM modules).
[092] [092] Similarly, network node 160 can be composed of multiple physically separate components (for example, a NodeB component and an RNC component, or a BTS component and a BSC component etc.), which can each one, have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In this scenario, each single pair of NodeB and RNC can, in some cases, be considered a single separate network node. In some embodiments, network node 160 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (for example, readable medium by separate device 180 for the different RATs) and some components can be reused (for example, the same antenna 162 can be shared by the RATs). Network node 160 can also include multiple sets of the various components illustrated for different wireless technologies integrated into network node 160, such as GSM, WCDMA, LTE, NR, WiFi or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or another chip or the chip set and other components within network node 160.
[093] [093] The processing circuitry 170 is configured to perform any determination, calculation or similar operations (e.g., certain procurement operations) described in the present invention as being provided by a network node. These operations performed by the processing circuitry 170 may include processing information obtained by the processing circuitry 170, for example, when converting the information obtained into other information, comparing the information obtained or information converted to the information stored in the network node and / or perform one or more operations based on the information obtained or converted and as a result of said processing make a determination.
[094] [094] The processing circuitry 170 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application-specific integrated circuit, an array of field programmable port or any other computing device, resource or combination of hardware, software and / or suitable coded logic operable to provide, alone or in conjunction with other network node components 160, such as device-readable medium 180, network node
[095] [095] In some embodiments, the processing circuitry 170 may include one or more radiofrequency (RF) transceiver circuits 172 and baseband processing circuitry 174. In some embodiments, the transceiver circuitry of 174 radio frequency (RF) 172 and the baseband processing circuitry 174 may be on separate chips (or chip sets), cards or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, cards or units.
[096] [096] In certain embodiments, part or all of the functionality described in the present invention as being provided by a network node, base station, eNB or other network device can be performed by the processing circuitry 170 executing instructions stored in the readable medium per device 180 or in memory within the processing circuit set 170. In alternative embodiments, some or all of the functionality can be provided through the processing circuit set 170 without executing instructions stored in a readable medium by a separate or discrete device, such as like in a wired way. In any of these modalities, whether executing instructions stored on a device-readable storage medium or not, the processing circuitry 170 can be configured to perform the described functionality. The benefits provided by this functionality are not limited only to the processing circuitry 170 or other components of network node 160, but are enjoyed by network node 160 as a whole and / or by end users and the wireless network in general.
[097] [097] Device-readable medium 180 may comprise any form of volatile or non-volatile computer-readable memory, including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, memory random access (RAM), read-only memory (ROM), mass storage media (for example, a hard drive), removable storage media (for example, a USB stick, a Compact Disc (CD) or a Video Disc Digital (DVD)) and / or any other memory devices readable by non-transitory and / or computer executable, volatile or non-volatile devices that store information, data and / or instructions that can be used by the processing circuitry 170. The device-readable medium 180 can store any appropriate instructions, data or information, including a computer program, software, an application that includes one or more of logic, rules , code, tables, etc. and / or other instructions capable of being executed by the processing circuitry 170 and used by the network node 160. Device-readable medium 180 can be used to store any calculations made by the processing circuitry 170 and / or any data received via interface 190. In some embodiments, the processing circuitry 170 and the device-readable medium 180 can be considered integrated.
[098] [098] Interface 190 is used to communicate with or without signaling and / or data between network node 160, network 106 and / or WDs 110. As illustrated, interface 190 comprises port (s) / terminal ( is) 194 to send and receive data, for example, to and from network 106 over a wired connection. Interface 190 also includes a radio front-end circuit set 192 that can be coupled to, or, in certain embodiments, a part of, antenna 162. The radio front-end circuit set 192 comprises filters 198 and amplifiers 196. The radio front-end circuitry 192 can be connected to antenna 162 and processing circuitry 170. The radio front-end circuitry can be configured to condition the signals communicated between antenna 162 and the processing circuitry 170. The radio frontend circuitry 192 can receive digital data that must be output to other network nodes or WDs via a wireless connection. The radio front-end circuitry 192 can convert the digital data into a radio signal with the appropriate channel and bandwidth parameters using a combination of filters 198 and / or amplifiers 196. The radio signal can then be transmitted via antenna 162. Likewise, when receiving data, antenna 162 can collect radio signals which are then converted into digital data by the 192 radio front-end circuitry. The digital data can be passed to the 170 processing circuits. In other embodiments, the interface may comprise different components and / or different combinations of components.
[099] [099] In certain alternative embodiments, network node 160 may not include separate radio front-end circuits 192, instead
[0100] [0100] Antenna 162 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. Antenna 162 can be coupled to the radio front-end circuitry 190 and can be any type of antenna capable of transmitting and receiving data and / or wireless signals. In some embodiments, antenna 162 may comprise one or more omnidirectional, sectorial or panel antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna can be used to transmit / receive radio signals. radio in any sense, a sector antenna can be used to transmit / receive radio signals from devices within a specific area and a panel antenna can be a line of sight antenna used to transmit / receive radio signals on a relatively line straight. In some cases, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 can be separated from network node 160 and can be connected to network node 160 via an interface or port.
[0101] [0101] Antenna 162, interface 190 and / or the processing circuitry 170 can be configured to perform any receive operations and / or certain obtain operations described in the present invention as being performed by a network node. Any information, data and / or signals can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 162, interface 190 and / or processing circuitry 170 can be configured to perform any transmission operations described in the present invention as being performed by a network node. Any information, data and / or signals can be transmitted to a wireless device, another network node and / or any other network equipment.
[0102] [0102] The power circuit set 187 can comprise or be coupled to a power management circuit set and is configured to supply power to the network node components 160 with power to perform the functionality described in the present invention. Power circuit set 187 can receive power from power source 186. Power source 186 and / or power circuit set 187 can be configured to supply power to the various components of network node 160 in a form suitable for the respective components (for example, at a voltage and current level required for each respective component). Power source 186 may be included in, or external to, power circuit set 187 and / or network node 160. For example, network node 160 may be connectable to an external power source (for example, a electricity outlet) via a circuitry or input interface as an electrical cable, whereby the external power supply supplies power to the power circuitry 187. As an additional example, power source 186 may comprise a power source power in the form of a battery or battery pack that is connected to or integrated with the 187 power circuit pack. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, can also be used.
[0103] [0103] Alternative modalities of network node 160 may include additional components in addition to those shown in FIGURE 6 that may be responsible for providing certain aspects of the functionality of the network node, including any of the features described in the present invention and / or any functionality necessary to support the matter described in the present invention. For example, network node 160 may include user interface equipment to allow information to enter network node 160 and to allow information to be output from the network node
[0104] [0104] As used in the present invention, the wireless device (WD) refers to a device capable, configured, organized and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise stated, the term WD can be used interchangeably in the present invention with user equipment (UE). Wireless communication may involve the transmission and / or reception of wireless signals using electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information over the air. In some embodiments, a WD can be configured to transmit and / or receive information without direct human interaction. For example, a WD can be designed to transmit information to a network at a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of WD include, but are not limited to, a smartphone, a mobile phone, a cell phone, a voice over phone.
[0105] [0105] As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, readable medium per device 130, user interface equipment 132, auxiliary equipment 134, power supply 136 and circuitry power 137. The WD 110 can include multiple sets of one or more of the components illustrated for different wireless technologies supported by the WD 110, such as GSM, WCDMA, LTE, NR, WiFi, WiMAX or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or chipsets as other components of the WD 110.
[0106] [0106] Antenna 111 can include one or more antennas or antenna arrays, configured to send and / or receive wireless signals and is connected to interface 114. In certain alternative embodiments, antenna 111 can be separated from WD 110 and connect to the WD 110 via an interface or port. Antenna 111, interface 114 and / or processing circuitry 120 can be configured to perform any receive or transmit operations described in the present invention as being performed by a WD. Any information, data and / or signals can be received from a network node and / or another WD. In some embodiments, the radio and / or antenna 111 front-end circuitry can be considered an interface.
[0107] [0107] As illustrated, interface 114 comprises radio front-end circuitry 112 and antenna 111. Radio front-end circuitry 112 comprises one or more filters 118 and amplifiers
[0108] [0108] The processing circuitry 120 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application-specific integrated circuit, an array of field programmable port or any other suitable computing device, resource or combination of hardware, software and / or operable coded logic to provide, alone or in conjunction with other WD 110 components, such as device readable medium 130, WD 110 functionality Such functionality may include providing any of the various wireless features or benefits discussed in the present invention. For example, the processing circuitry 120 can execute instructions stored in the device-readable medium 130 or in memory within the processing circuitry 120 to provide the functionality disclosed in the present invention.
[0109] [0109] As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124 and application processing circuitry 126. In other embodiments, the The processing circuit assembly may comprise different components and / or different combinations of components. In certain embodiments, the processing circuitry 120 of WD 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124 and application processing circuitry 126 may be on separate chips or chip sets. In alternative embodiments, part or all of the baseband processing circuitry 124 and application processing circuitry 126 may be combined on a chip or chip set and the RF transceiver circuitry 122 may be in one separate chip or chip set. In still alternative embodiments, part or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 may be on the same chip or chip set, and the application processing circuitry 126 may be in a separate chip or chip set. In yet other alternative embodiments, part of or all of the RF transceiver circuitry 122, baseband processing circuitry 124 and application processing circuitry 126 may be combined on the same chip or chip set. In some embodiments, the RF transceiver circuitry 122 may be an interface part
[0110] [0110] In certain embodiments, part or all of the functionality described in the present invention as being performed by a WD can be provided by the processing circuitry 120 executing instructions stored in device-readable medium 130, which in certain embodiments can be a means computer-readable storage. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 120 without executing instructions stored in a separate or discrete device-readable storage medium, such as in a wired manner. In any of these particular embodiments, whether executing instructions stored on a device-readable storage medium or not, the processing circuitry 120 can be configured to perform the described functionality. The benefits provided by this functionality are not limited only to the processing circuitry 120 or other components of the WD 110, but are enjoyed by the WD 110 as a whole and / or by the end users and the wireless network in general.
[0111] [0111] The processing circuitry 120 may be configured to perform any determination, calculation or similar operations (for example, certain procurement operations) described in the present invention as being performed by a WD. These operations, as performed by the processing circuitry 120, may include processing information obtained by the processing circuitry 120, for example, when converting the information obtained into other information, comparing the information obtained or information converted to the information stored by the WD 110 and / or perform one or more operations based on the information obtained or converted and, as a result of said processing, make a determination.
[0112] [0112] The device-readable medium 130 can be operable to store a computer program, software, an application that includes one or more among logic, rules, code, tables etc. and / or other instructions capable of being executed by the processing circuitry 120. The device-readable medium 130 may include computer memory (for example, Random Access Memory (RAM) or Read-Only Memory (ROM)), media mass storage (for example, a hard drive), removable storage media (for example, a Compact Disc (CD) or Digital Video Disc (DVD)) and / or any other volatile or non-volatile memory devices, readable by non-transitory device and / or executable by computer that store information, data and / or instructions that can be used by the processing circuitry 120. In some embodiments, the processing circuitry 120 and the device-readable medium 130 can be considered integrated.
[0113] [0113] User interface equipment 132 can provide components that allow a human user to interact with WD 110. Such interaction can take many forms, such as visual, auditory, tactile, etc. User interface equipment 132 can be operable to produce output for the user and allow the user to provide input to WD 110. The type of interaction may vary depending on the type of user interface equipment 132 installed on the WD 110. For example , if the WD 110 is a smartphone, the interaction can be via touch screen; if the WD 110 is a smart meter, the interaction can be through a screen that provides use (for example, the number of gallons used) or a speaker that provides an audible alert (for example, if smoke is detected) . User interface equipment 132 may include interfaces, devices and input circuits and interfaces, devices and output circuits. User interface equipment 132 is configured to allow information to be input to the WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process input information. User interface equipment 132 may include, for example, a microphone, a proximity sensor or the like, keys / buttons, a touch sensitive display, one or more cameras, a USB port or other sets of input circuits. User interface equipment 132 is also configured to allow information to be output from WD 110 and to allow processing circuitry 120 to output information from WD 110. User interface equipment 132 may include, for example, a speaker, a display, a set of vibrating circuits, a USB port, a headset interface, or other set of output circuits. Using one or more interfaces, devices and input and output circuits of the 132 user interface equipment, the WD 110 can communicate with end users and / or the wireless network and allow them to benefit from the functionality described in the present invention. .
[0114] [0114] Auxiliary equipment 134 is operable to provide more specific functionality which generally cannot be performed by WDs. This can comprise specialized sensors for making measurements for various purposes, interfaces for additional types of communication, such as wired communications, etc. The inclusion and type of auxiliary equipment components 134 may vary depending on the modality and / or scenario.
[0115] [0115] Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (for example, an electrical outlet), photovoltaic devices or power cells, can also be used. The WD 110 can additionally comprise the power circuit set 137 for delivering power from the power source 136 to the various parts of the WD 110 that need power from the power source 136 to perform any functionality described or indicated in the present invention. . The power circuitry 137 may, in certain embodiments, comprise power management circuitry. The power circuit assembly 137 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 110 can be connected to the external power source (such as an electrical outlet) via an input circuit assembly or an interface such as an electrical power cable. The power circuit assembly 137 may also, in certain embodiments, be operable to deliver power from an external power source to the power source 136. This may be, for example, for charging the power source 136. The power circuit assemblies 137 can perform any formatting, conversion or other modification in the power of the power source 136 to make the power suitable for the respective components of the WD 110 to which the power is supplied.
[0116] [0116] As described above, and NR WD 110 may be required to switch from a first BWP (that is, a source BWP) to a second BWP (that is, a destination BWP). The need for the WD110 to switch to BWP can cause problems with RLM and RLF, as described above. As described in detail below, the various modalities described in the present invention relate to actions performed by a WD (for example, WD 110) and the network (for example, network node 160) in the context of configuring RLM and RLF by switching BWP which can solve these and / or other problems related to switching BWP.
[0117] [0117] In certain embodiments, the WD 110 (for example, a UE) obtains one or more RLM configurations. Each RLM configuration can be associated with at least one BWP. For example, one or more RLM configurations can include an RLM configuration associated with a target BWP. In certain embodiments, network node 160 (for example, m gNB) can determine one or more RLM configurations.
[0118] [0118] The WD 110 can obtain these one or more RLM configurations in any suitable manner. As an example, WD 110 can be configured by network node 160 with one or more RLM configurations. for example, the WD 110 can obtain one or more RLM configurations by receiving the one or more RLM configurations in a message from the network node (160). In some cases, the message from network node 160 can be sent as part of network nodes 160 by configuring WD 110 to perform RLM on a BWP (for example, a destination BWP) according to an RLM configuration associated with that BWP . In certain embodiments, the message may include an indication of the RLM configuration associated with that BWP. In some cases, the indication may be included in an IE within a BWP configuration for BWP. In some cases, the indication may be included in an IE within a server cell configuration. In some cases, the indication may comprise an RLM configuration identifier.
[0119] [0119] As another example, the WD 110 can obtain one or more RLM configurations when determining one or more RLM configurations (for example, according to one or more predefined rules). For example, the WD 110 can determine one or more RLM configuration parameters. In some cases, the determination can be based on an active BWP or a set of active BWPs. In certain embodiments, network node 160 can configure WD 110 to determine the RLM configuration associated with a BWP according to one or more predefined rules.
[0120] [0120] In certain modalities, one or more of the obtained RLM configurations can be an active RLM configuration. In certain embodiments, the WD 110 can determine that one of the RLM configurations is an active RLM configuration. The WD 110 can determine that one of the RLM configurations is an active RLM configuration in any suitable manner. As an example, WD 110 can be configured by network node 160 with an active RLM configuration. In other words, one of the one or more RLM configurations obtained can be configured by network node 160 as an active RLM configuration. As another example, the WD 110 can determine the active RLM configuration (for example, based on a predefined rule).
[0121] [0121] In certain embodiments, one of the one or more RLM configurations obtained can be a standard RLM reconfiguration. The default RLM configuration can be configured over the network (for example, network node 160), specified by the standard, and / or determined by WD 110 (for example, based on a predefined rule). In some cases, the default RLM configuration can be associated with the default BWP. In some cases, the default RLM configuration may not be associated with the default BWP.
[0122] [0122] Each RLM configuration can include information related to RLM. In general, each RLM configuration includes a set of radio features to perform radio link monitoring within its associated BWP, as well as one or more configuration parameters to perform RLM within its associated BWP. Examples of radio resources include the CSI-RS, SSB (also known as SS / PBCH or SS Block) or other radio resources suitable for RLM. Examples of configuration parameters for performing RLM that can be included in the RLM configuration are filtering parameters (for example, counters N310, N311, N313, N314 or other suitable counter), RLF timer (s) (for example, RLF timers T310, T311, T313, T314 or other suitable timer), an evaluation period, a number of retransmissions before the RLF is declared, a hypothetical channel / signal configuration, a mapping function between the measured link quality and the hypothetical BLER channel, or other suitable configuration parameters. The information that can be included in an RLM configuration is described in more detail below.
[0123] [0123] In certain embodiments, each RLM configuration may include one or a combination of the following types of information.
[0124] [0124] Each RLM configuration can include the type (s) of RS that should be monitored for RLM (ie PBCH / SS Block, CSI-RS or a combination of CSI-RS and SSB features).
[0125] [0125] Each RLM configuration can include features specific to the type of RS configured to be monitored for RLM. As an example for cases where CSI-RS resources are used, each RLM configuration can include the RLM CSI-RS resources in time / frequency and the exact sequence. As another example for cases where SS / PBCH Block features are used, each RLM configuration can include specific SS / PBCH Block indexes. In certain embodiments, the specific SS / PBCH Block indices can be derived by WD 110. In certain embodiments, the specific SS / PBCH Block indices can be indicated explicitly. As another example for cases where a combination of SSB and CSI-RS features are used, each RLM configuration can include the combination of SSB and CSI-RS features (for example, time-specific CSL / RS RLM features / frequency and exact sequence as well as specific SS / PBCH Block indices).
[0126] [0126] Each RLM configuration can include limits related to link and / or channel quality (for example, SINR limits and / or a pair of BLER limits for generating OOS and IS events). These parameters can change when BWPs are changed.
[0127] [0127] Each RLM configuration can include one or more timers or counters related to RLM / RLF (for example, timer T310 and counter N310). Other timers and counters may be included in addition (or as an alternative), as other types of timers and counters described in the present invention.
[0128] [0128] Each RLM configuration can include one or more parameters that determine the mapping between SINR and BLER, or a mapping function, mapping rule or mapping table. Note that the mapping to be used by the WD 110 can be configured or controlled explicitly by the network (for example, by the network node 160).
[0129] [0129] Each RLM configuration can include a compensation factor to be applied to SINR prior to mapping to a channel quality (for example, a hypothetical BLER control channel). In certain embodiments, the compensation factor may depend, for example, on one or more of BWP, type of RLM resources, BLER, measurement bandwidth for RLM, numerology (such as subcarrier spacing, symbol length, or length cyclic prefix (CP)), frequency and any other suitable criteria.
[0130] [0130] Each RLM configuration can include an evaluation period for RLM and / or the number of samples to be used for link evaluation.
[0131] [0131] Each RLM configuration can include one or more hypothetical channel configuration parameters (for example, a hypothetical PDCCH), such as one or more of bandwidth, aggregation level, DCI size, a number of symbols, a control channel power ratio to SSS resource element (RE) energy, or other suitable configuration parameters.
[0132] [0132] In certain embodiments, the WD 110 can obtain an RLF / SCG fault configuration. In some cases, the RLF / SCG failure configuration can be included in the RLM configuration. In some cases, the RLF / SCG failure configuration can be separated from the RLM configuration. In such a scenario, the WD 110 can obtain the RLF / SCG failure configuration in a manner similar to that described above in relation to the WD 110 obtaining one or more RLM configurations. In certain embodiments, each RLF / SCG failure configuration can include one or more of the following: timers (for example, one or more of the T310, T311, T313, T314 timers); and counters (for example, one or more of counters N310, N311, N313, N314).
[0133] [0133] In certain modalities the WD 110 determines that the WD 110 must switch from a source BWP to a destination BWP. For example, the WD 110 can receive an instruction to switch from a source BWP to a destination BWP (for example, via DCI). The WD 110 performs RLM on the destination bandwidth portion according to an obtained RLM configuration associated with the destination BWP. In certain modalities, by activating a new BWP, the WD 110 can activate an RLM configuration previously configured based on various rules and / or criteria.
[0134] [0134] In an exemplary mode, one or more of the target BWP and source BWP can be a DL BWP (for example, for a paired spectrum or FDD). In another exemplary embodiment, one or more of the target BWP and source BWP can be a DL / UL BWP (for example, for unpaired spectrum or TDD), where the DL BWP and UL BWP have the same frequency center and they are activated simultaneously, although they may have the same or different bandwidths. In yet another exemplary modality, one or more of the target BWP and source BWP can be a UL BWP, which potentially can also impact how the RLM / RLF is configured.
[0135] [0135] Now, to illustrate the above, a specific exemplary modality will be described. The WD 110 can obtain K1 RLM configurations that are associated with K2 BWP configurations (for example, the RLM k1 * configuration is associated with the BWP k2 * configuration). As described above, WD 110 can obtain K1 RLM settings based on a message received from network node 160 and / or determine K1 RLM settings (for example, based on a predefined rule). The WD 110 can determine (for example, derive based on a predefined rule or pattern or select from a set of predefined values) at least one RLM configuration parameter for at least one RLM configuration outside the K1 settings RLM. Upon triggering the activation of a given BWP (for example, k2 *), the WD 110 activates the associated RLM configuration, k1 *.
[0136] [0136] The RLM and BWP configurations can be associated in a variety of ways. As a first example, each RLM configuration can be provided as an IE within each BWP configuration. As a second example, each RLM configuration can be provided as an IE within the server cell configuration and associated with an RLM configuration identifier, where only the RLM configuration identifier is part of each BWP configuration IE. This advantageously allows RLM configurations to be transmitted efficiently in RRC signaling. As a third example, each RLM configuration can be provided as an IE within the server cell configuration, and there can be a list of BWP IDs within each RLM configuration IE. The configuration of RLM by BWP can be OPTIONAL fields in the configuration of BWP in any of the cases mentioned above. In other words, there may be a standard cell-based RLM configuration that is assumed if the WD 110 is switched to a BWP without the RLM configuration.
[0137] [0137] The settings of the source BWP (that is, old) and the destination BWP (that is, new active) can be the same or different in terms of the type of RS. Different combinations may exist as described in more detail below. As a first example, the RLM configuration associated with the source BWP configuration can define the Type of RS = SS block and the RLM configuration associated with the destination BWP configuration can also define the Type of RS = SS block. In some cases, the new (ie, target) SSB for RLM measurements may be in the same frequency position as the old (ie, source) SSB. In some cases, the new SSB for RLM measurements may be in a different frequency position than the old SSB. In some cases, the new SSB for RLM measurements may have the same time domain pattern as the old SSB. In some cases, the new SSB for RLM measurements may have a different time domain pattern than the old SSB. In some cases, the new SSB for RLM measurements may have the same physical cell identifier (PCID) as the old SSB. In some cases, the new SSB for RLM measurements may have a different PCID than the old SSB. In some cases, the new SSB for RLM measurements may define the same RLM resources (that is, SSB indexes) as the old SSB. In some cases, the new SSB for RLM measurements may define different RLM resources (that is, SSB indexes) compared to the old SSB. These can be additional or minor features.
[0138] [0138] As a second example, the RLM configuration associated with the source BWP configuration can define the Type of RS = CSI-RS and the RLM configuration associated with the destination BWP configuration can define the Type of RS = CSI- LOL. In some cases, the new CSI-RS features for RLM measurements may be in the same frequency position as an old CSI-RS feature. In some cases, the new CSI-RS features for RLM measurements may be in a different frequency position than an old CSI-RS feature. In some cases, the old and new CSI-RS configuration can define the same CSI-RS measurement bandwidth. In some cases, old and new CSI-RS configurations can define different CSI-RS measurement bandwidths. In some cases, the new CSI-RS resource (s) for RLM measurements may have the same time domain pattern as the old CSI-RS resource (s) (s) for RLM. In some cases, the new CSI-RS resource (s) for RLM measurements may have a different time domain pattern than the old CSI-RS resource (s) ) for RLM. In some cases, the new CSI-RS resource (s) for RLM measurements may be in the same sequence as the old CSI-RS resource (s) ). In some cases, the new CSI-RS resource (s) for RLM measurements may have a different sequence from the old CSI-RS resource (s). In some cases, the new CSI-RS features for RLM measurements may define the same RLM features (that is, CSI-RS time / frequency / sequence) as the old CSI-RS. In some cases, the new CSI-RS resources for RLM measurements may define different RLM resources (that is, CSI-RS time / frequency / sequence) than the old CSI-RS.
[0139] [0139] In cases where the RLM RS is CSI-RS, the WD 110 can be configured over the network (for example, network node 160) with one or multiple RLM configurations based on one or multiple resource sets (s) of CSI-RS, possibly allocated in different portions of the bandwidth of the entire cell (that is, comprising multiple BWPs). Therefore, by switching to a new active BWP, the WD 110 stops using the CSI-RS resource (s) previously used within the source BWP for RLM (ie, the WD 110 stops playing measurement (s) in the CSI-RS resource (s) used previously and stops mapping them to the BLER limits to generate IS / OOS events) and starts using the resource (s) ) of CSI-RS configured (s) within the new BWP for RLM (that is, the ED 110 performs SINR measurements to be mapped to the configured BLER values).
[0140] [0140] In certain modalities, multiple CSI-RS resources configured may be within the new BWP. In such a scenario, network node 160 can configure WD 110 to select one or more sets of radio resources to be used to perform RLM on the target BWP (for example, based on a predefined rule). The WD 110 can select one or more of these radio resource sets to be used to perform RLM on the target BWP (for example, based on the predefined rule). The WD 110 can determine which CSI-RS features are used for monitoring RLM in any appropriate manner. In certain embodiments, this determination can be based on a predefined rule (for example, a rule that governs which WD 110 is to be used for RLM monitoring. As another example, the rule may be that WD 110 selects the CSI- RS with the highest frequency component to be used for RLM monitoring As another example, the rule may be that the WD 110 performs RLM measurements on all CSI-RSs configured within the BWP. 110 can be configured to arbitrarily choose one of the multiple CSI-RS features configured for RLM monitoring.
[0141] [0141] Similarly, multiple SSB configurations and corresponding WD behavior are feasible when the RS types of RLM are set to SSB. In other words, network node 160 can configure WD 110 to select one or more sets of radio resources (in this instance, SSB resources) to use to perform RLM in the target bandwidth portion, and WD 110 can select one or more from the plurality of radio resource sets to be used to perform RLM on the target BWP part (for example, based on a predefined rule such as those described above for scenarios in which multiple sets of CSI resources - RS are configured).
[0142] [0142] In certain embodiments, network node 160 can provide multiple configurations of RLM RS associated with the same BWP (for example, one or more RS configurations for each of the configured BWPs). For example, network node 160 can provide WD 110 with an RLM configuration using SSB and an RLM configuration using CSI-RS, both of which are associated with the same BWP. As another example, network node 160 can provide WD 110 with multiple RS configurations of the same type of RS (for example, two RLM configurations that use a CSI-RS configuration, or use an SSB). In any exemplary scenario, network node 160 can indicate (for example, in DCIs requesting BWP switching) which of the RS configurations associated with the destination BWP should be used for RLM. In certain embodiments, network node 160 can also activate a corresponding RS (unless, for example, it has already been activated by another WD using the same BWP).
[0143] [0143] In certain modalities, the use of different BLER limit settings can be treated in a similar way. In other words, there can be multiple BLER limit configurations associated with the same BWP and network node 160 can provide WD 110 with an indication of which of the multiple BLER limit configurations should be used with the BWP for RLM.
[0144] [0144] Alternatively, in certain embodiments, network node 160 may provide a list of RLM RS configurations without association with BWPs. In such a scenario, network node 160 can indicate in DCIs that request a BWP switching which of the listed RS configurations should be used for RLM in the new BWP. Different BLER limit settings can also be treated in the same way.
[0145] [0145] In addition to the examples described above, there are a variety of other ways in which an RLM / RLF configuration can be associated with a BWP, including the exemplary rules described below. These rules can be used by the network (for example, network node 160) that configures RLM / RLF and BWPs (or the association between BWP and RLM / RLF configurations) or by the WD 110 that selects the appropriate RLM / RLF configuration using changing the set of active BWPs. Examples of rules that can be used to associate an RLM / RLF configuration with a BWP in certain modalities are described in more detail below.
[0146] [0146] As a first exemplary rule, in certain embodiments RLM is based on a first bandwidth (BW1) (for example, SSB for SSB-based RLM or CSI-RS for CSI-RS-based RLM) when a first BWP (BWP1) is active, while RLM is based on a second bandwidth (BW2) (for example, SSB for SSB-based RLM or CSI-RS for CSI / RS-based RLM) when a second BWP (BWP2) is active. In such a scenario, the first bandwidth is less than or equal to the second bandwidth (that is, BW1 <= BW2) and the bandwidth of BWP1 is not greater than the bandwidth of BWP2.
[0147] [0147] As a second exemplary rule, in certain embodiments a first type of RLM RS (for example, signals comprised in the SS Block) is used when the SS Block is comprised within a BWP, while a second type of RLM RS (for example, CSI-RS) is used in another way.
[0148] [0148] As a third exemplary rule, in certain modalities a first type of limits, timers and / or counters is used when the RLM is based on a first type of RLM RS (for example, based on SS Block), while a second type of limits, timers and / or counters is used when the RLM is based on a second type of RLM RS (for example, CSI-RS).
[0149] [0149] As a fourth exemplary rule, in certain modalities a first compensation factor is applied when a first BWP is active, while a second compensation factor is applied when a second BWP is active. In such a scenario, at least one of the first and second compensation factors changes the RLM measurement (for example, SINR) to a different value (for example, nonzero compensation factor if added for SINR or not equal to 1 if scales the SINR).
[0150] [0150] As a fifth exemplary rule, in certain modalities a set of configuration parameters (for example, bandwidth, aggregation level, DCI size, number of symbols, control channel energy rate for SSS RE energy , etc.) of the hypothetical channel (for example, a hypothetical control channel) is used when a first BWP is active, while a second set of configuration parameters for the hypothetical channel is used when a second BWP is active.
[0151] [0151] As a sixth exemplary rule, in certain modalities a longer RLM evaluation period for a first RLM RS (for example,
[0152] [0152] As a seventh exemplary rule, in certain embodiments the evaluation period is extended if the hypothetical channel and / or BWP bandwidth is reduced, while the evaluation period is reduced if the channel bandwidth and / or Hypothetical BWP increase. In certain modalities, the evaluation period may be the longest between the evaluation periods that correspond to the new and the old BWP during the transition time (that is, when the evaluation period does not restart by changing the BWP).
[0153] [0153] As described above, performing RLM implies using measurements to generate OOS and IS events. In certain modalities, the WD 110 can perform specific actions related to measurements when it needs to change the BWP. These actions can be related to, for example, whether (and how) measurements performed on a previous BWP can be used on a newly activated BWP, how the OOS and IS events generated in the previous BWP can be used and how the WD 110 and the node network managers manage counters (for example, counters N310, N311, N313, N314) and timers (for example, timers T310, T311, T313 and T314) for these events. Several exemplary modalities that concern how the WD 110 handles its measurements when changing BWP are described in detail below.
[0154] [0154] For example, in some cases the hypothetical channel configuration used for RLM may be different for the new BWP. In such a scenario, the WD 110 can update the hypothetical channel configuration used for RLM. Similarly,
[0155] [0155] As another example, in some cases the evaluation period for the newly active BWP may be different. In such a scenario, the WD 110 can change the RLM evaluation period. For example, the evaluation period can be changed as described above in relation to the sixth and seventh exemplary rules for associating an RLM / RLF configuration with a BWP).
[0156] [0156] In some cases, the same type and resources of RS can be used in the newly active BWP (ie, the destination BWP). In such a scenario, the WD 110 can continue to use previously performed measurements or measurement samples to generate OOS and IS events (ie, the WD 110 continues to count). In certain embodiments, the WD 110 maintains the counter variables (for example, N310, N311, N313, N314). Thus, the counter variables continue to increase / decrease based on the generated OOS and / or IS events. In other words, from a top layer perspective, how IS / OOS events are generated remains transparent. In certain embodiments, network node 160 can configure WD 110 to use one or more of the measurements previously performed and samples of measurements previously performed to generate OOS and IS events when the same type and RS features are used in the newly BWP active.
[0157] [0157] In some cases, however, RLM measurements may not be able to be reused when a new BWP is activated. If the RLM measurements cannot be reused when a new BWP is activated, the WD 110 can reset one or more timers or counters. Otherwise (that is, if the RLM measurements can be reused), the WD 110 can continue to use at least one of the timers or counters (for example, as described above).
[0158] [0158] When different resources are used in the newly active BWP, there are a variety of ways in which the WD 110 can handle the counters and timers used to generate IS / OOS events. Different exemplary modalities that detail ways in which the WD 110 behaves when different features are used in the newly active BWP are described in more detail below.
[0159] [0159] In an exemplary embodiment, if different RLM RS are used for different BWPs, the WD 110 applies a measurement function to allow RLM assessments to continue and to allow timers and counters to continue. In one example, the relation function can be an offset applied to SINR based on a first RLM RS compared to that based on a second RLM RS. In certain embodiments, network node 160 can configure WD 110 to apply a relationship function to one or more measurements previously performed and samples of measurements previously performed to generate OOS and IS events without resetting an RLF timer or RLF counters when different RLM RS are used in the newly active BWP.
[0160] [0160] In another exemplary mode, the WD 110 resets at least one of the timers or counters when the RLM RS is different by changing the BWP. In certain embodiments, network node 160 can configure WD 110 to reset at least one RLF timer and RLF counters when different resources are used in the newly active BWP.
[0161] [0161] In another exemplary mode, the WD 110 resets one of the timers and counters (for example, for RLM OOS) and allows another set of timers and counters to continue (for example, for RLM IS). In certain embodiments, network node 160 can configure WD 110 to reset a set of RLF timers and RLF counters (for example, for OOS events) and configure WD 110 to allow a set of RLM timers and counters RLF (for example, for IS events) continue when different RLM RS are used in the newly active BWP.
[0162] [0162] In another exemplary mode, the WD 110 allows timers to continue, but not counters. In certain embodiments, network node 160 can configure WD 110 to reset one or more RLF timers without resetting any RLF counters when different RLM RS are used in the newly active BWP.
[0163] [0163] In another exemplary embodiment, the WD 110 applies an offset (for example, to extend the time or increase the number of RLM physical layer reports allowed before triggering an action) for at least one counter or timer. In certain embodiments, network node 160 can configure WD 110 to apply an offset to at least one counter or timer when different RLM RS are used in the newly active BWP.
[0164] [0164] As described above, the WD 110 can obtain an RLF / SCG fault configuration and each RLFSCG fault configuration can include one of the following or a combination of these parameters: timers (for example, one or more T310, T311 timers , T313, T314); and counters
[0165] [0165] In some cases, at least one of the timers that trigger RLF or SCG Failure (for example, the T310 or T313 timer) can be performed when a BWP switch is triggered. Several exemplary actions that can be taken by the WD 110 if any of the timers that trigger RLF or SCG Failure are running when the BWP switch is triggered are described in more detail below. For the purposes of the following examples, it must be assumed that one of the timers that trigger an RLF or SCG fault is running when the BWP switch is triggered.
[0166] [0166] As a first example, in some cases the RLM RS type can be SSB in both the old BWP (ie source) and the new BWP (ie target) and the new BWP may not have an SSB associated with it within the newly active BWP. In other words, the WD 110 can be configured to continue using the same SSB for RRM and RLM measurements. In such a scenario, in certain modalities the WD 110 performs the following actions: The WD 110 does not reset the timer (s); the WD 110 does not rule out previously performed measurements; the WD 110 does not discard previously generated IS / OOS events; and the WD 110 continues to increment the counter (s).
[0167] [0167] As a second example, in some cases the RLM RS type in the old BWP may have been SSB or CSI-RS and the RLM RS type may be SSB in the new BWP. In addition, the new BWP may have a new SSB associated with it within the newly active BWP to be used for RRM and / or RLM measurements. In such a scenario, in certain modalities the WD 110 performs the following actions: The WD 110 resets the timer (s); the WD 110 discards measurement (s)
[0168] [0168] As a third example, in some cases the RLM RS type may be CSI-RS in both the old and the new BWP and the new BWP may not have a new CSI-RS configuration associated with it in the newly active BWP . In other words, WD 110 can be configured to continue using the same CSI-RS configuration for RRM and RLM measurements. In such a scenario, in certain modalities WD 110 performs the following actions: WD 110 does not reset the timer (s); WD 110 does not rule out measurement (s) performed previously; WD 110 does not discard previously generated IS / OOS event (s); and WD 110 continues to increment the counter (s).
[0169] [0169] As a fourth example, in some cases the RLM RS type in the old BWP may have been SSB or CSI-RS and the RLM RS type may be CSI-RS in the new BWP. Additionally, the new BWP may have a new CSI-RS configuration associated with it in the newly active BWP. In such a scenario, in certain modalities WD 110 performs the following actions: WD 110 does not reset the timer (s); WD 110 does not rule out measurement (s) performed previously; WD 110 does not discard previously generated IS / OOS event (s); WD 110 continues to increment the counter.
[0170] [0170] As a fifth example, in some cases the RLM RS type in the old BWP may have been SSB or CSI-RS and the RLM RS type may be CSI-RS in the new BWP. Additionally, the new BWP may have a new CSI-RS configuration associated with it in the newly active BWP. In such a scenario, in certain modalities WD 110 performs the following actions: WD 110 resets the timer (s); WD 110 discards measurement (s) previously performed; WD 110 discards previously generated IS / OOS event (s); and WD 110 resets the counter (s).
[0171] [0171] Note that with respect to the various exemplary modalities described above related to actions performed by the WD 110 when at least one of the timers that trigger an RLF or SCG fault is running when the BWP switch is triggered, the actions described as performed by the WD 110 can be performed in any order and the present invention is not limited to performing the actions in the order described above.
[0172] [0172] In addition, the actions described above that can be performed by WD 110 in certain scenarios are not intended to be limiting or exhaustive. In some cases, other actions by the WD 110 may be appropriate in conjunction with WBP switching for different cases of the RLM RS type. Thus, in certain modalities the opposite behavior (or variations in the example modalities described above) can be used in some switching cases. Therefore, in other modalities, when WD 110 switches from one BWP to another, where the new BWP has a new type of RS or a new configuration for the same type of RS, WD 110 can keep timer (s) and counter (es) ) in execution and maintain previously performed measurement (s) and previously generated IS / OOS event (s). In certain embodiments, this can be broken down into finer granular modalities. For example, WD 110 can keep timer (s), counter (s), measurement (s) and event (s) if the type of RS is the same in the new BWP, but otherwise not.
[0173] [0173] In certain modalities, the actions taken by the WD 110 to reset the timer (s) and / or counter (s) or to maintain them based on an update to RLM resource settings can be configured over the network . The logic behind not changing the RLM state variables is that WD 110 still remains in the same cell. So if WD 110 had trouble synchronizing and had good enough channel quality in the old BWP, changing the BWP would probably not change that. On the other hand, as a change in BWP leads to (or at least can lead to) a PDCCH configuration update (for example, CORESET configuration update), which can also change the PDCCH beam forming properties, the network may want to redefine the state variables related to RLM and RLF.
[0174] [0174] In certain modalities, the network (for example, network node 160) can configure the actions to be taken by the WD 110 in relation to the reset or maintenance of the timer (s) and / or counter (s) (such as various actions by the WD 110 described above) in several ways. In certain modalities, the configuration of the actions performed by the WD 110 can be provided when the BWPs are configured. For example, in the form of a single general action rule setting that can be applied to all BWP switches. In certain embodiments, the general action rule setting can specify that the same actions must be performed regardless of the BWPs involved in the switch. In certain embodiments, the general action rule setting may specify that different actions are to be performed depending on the type of BWP switch (for example, in terms of the different scenarios above, ie changing the type of RS or not, changing configuration of RS resources or not). Alternatively, in certain modalities the network can configure separate actions associated with each configured BWP. For example, actions associated with a particular BWP can be performed when WD 110 switches to that specific BWP. As another example, actions associated with a particular BWP can be performed when the UE switches from that particular BWP to another BWP. As yet another example, network node 160 (for example, a gNB) can provide a list of action settings for WD 110. The list of action settings may not include BWP associations. Network node 160 can indicate (for example, in the DCI requesting a BWP switch) which of the listed action configurations WD 110 should be applied in conjunction with the BWP switch in question.
[0175] [0175] In certain embodiments, WD 110 can estimate the radio link quality to monitor the DL link quality (for example, based on CSI-RS or SSB signals) for RLM purposes (for example, for evaluations OOS and IS) on at least two different BWPs over at least a partially overlapping time period (for example, evaluation periods). In some cases, this may be referred to in the present invention as "parallel monitoring" or "partial parallel monitoring" of DL link qualities in different BWPs for RLM.
[0176] [0176] In some cases, the quality of a better beam in each sample may be relevant for generating OOS / IS events. Examples of OOS and IS evaluation periods for CSI-RS-based RLM are 100ms and 200ms, respectively (for example, when the OOS / IS evaluation is based on the quality of the DL link measured in CSI-RS). Examples of OOS and IS evaluation periods for SSB-based RLM are 3 * TSSB and 6 * TSSB, respectively (for example, when the OOS / IS evaluation is based on the DL link quality measured on SSB signals and where T SSB is the SS burst frequency set in the WD 110 for RLM.
[0177] [0177] As described in more detail below, according to an example of modality WD 110 can perform parallel monitoring of the DL link qualities in two or more BWPs regardless of the rate at which these BWPs are activated. In another example of a modality, WD 110 can perform parallel monitoring of the DL link qualities on two or more BWPs depending on the rate at which these BWPs are activated. For example, WD 110 can perform parallel monitoring of DL link qualities on any two BWPs as long as the UE is configured to activate each BWP for a certain period of time at least once each T1 time unit (for example, T1 = 10ms). For example, this rule will require the WD 110 to monitor the DL link quality on two or more BWPs in parallel only if those BWPs remain active continuously for a shorter period (for example, less than the link quality evaluation period DL radio).
[0178] [0178] In certain modalities, WD 110 can be configured to perform parallel evaluation (that is, for at least a partially overlapping period of time) of DL link quality on two or more BWPs in parallel selectively and / or based on one or more criteria. The criteria can be any suitable criteria. Examples of criteria include, but are not limited to: a duration for which the UE remains active on one or more configured BWPs; and a rate at which WD 110 is switched between different active BPWs. More specifically, WD 110 can be additionally configured to perform a parallel DL link quality assessment on two or more BWPs in parallel for at least a partially overlapping period of time based on the duration for which one or more of the BWPs remain active for the UE.
[0179] [0179] To illustrate, consider the following example of modality. For the purposes of this example, assume that WD 110 is configured (for example, via RRC) with two BWPs: a first BWP (BWP1) and a second BWP (BWP2). Suppose further that in a time instance, WD 110 can be configured (for example, via DCI) with only one active BWP (ie, the activated or active BWP of WD 110 is BWP1 or BWP2 in the current example). If WD 110 is configured with BWP1 active or BWP2 active for a duration less than a certain time limit (Ta), then WD 110 can perform DL radio link monitoring of DL signals on BWP1 and BWP2 whenever WD 110 become active in the respective BWP. However, if WD 110 is configured with BWP1 active or BWP2 active for a duration equal to or greater than the time limit Ta, then WD 110 performs DL RLM of DL signals only on the BWP that remains active after Ta. Examples of TA include 10 ms, 100 ms, etc.
[0180] [0180] In the first case (when BWP1 or BWP2 is active for less than the time limit Ta), in certain modalities WD 110 can further evaluate the OOS or IS detection based on a combination of the DL radio link qualities measured through BW1 and BW2. As another example, in certain modalities WD 110 can independently evaluate the detection of OOS and IS based on the radio link qualities measured through BW1 and BW2. In certain embodiments, whether WD 110 should use a combined metric for OOS and IS detection or independently apply DL radio link qualities for OOS and IS detection can be predefined as a rule in the standard. In certain embodiments, whether WD 110 should use a combined metric for detecting OOs and IS or independently applying DL radio link qualities for detecting OOS and IS can be configured in the UE by network node 160 (for example, via RRC , MAC and / or DCI via PDCCH or some other suitable way). Examples of metrics to achieve a combination of DL radio link qualities include, but are not limited to, average, maximum, minimum, or some other suitable metric. This mechanism will improve RLM performance and lead to power savings on the WD 110 since WD 110 does not need to perform parallel evaluation to detect OOS and IS in multiple BPWs all the time (instead, it can do so selectively).
[0181] [0181] In certain modalities, WD 110 can be configured with N BWPs. One of the configured N BWPs can be configured as a standard BWP. In such a scenario, in certain modalities WD 110 can always estimate the radio link quality to monitor DL link quality (for example, based on CSI-RS or SSB signals) in the standard BWP. In addition, in certain modalities WD 110 can monitor the radio link quality of the current active BWP when the current active BWP is not the standard BWP. In some cases, a timer can be used (for example, WD 110 can return to the default BWP if WD 110 cannot receive DCI on the active BWP for a certain time T). If WD 110 is monitoring the radio link quality of two different BWPs, the OOS and IS indications can be associated with an indication (for example, a tag) indicating which BWP caused the indication.
[0182] [0182] In certain embodiments, WD 110 can be configured to store BWP configuration information (for example, related to RLM and RLF configuration) in the RLF report that can be transmitted to the network after reset (for example, after the occurrence of RLF). In certain modalities, information can be stored when RLF occurs in a given BWP. WD 110 can include in an RLF report the BWP configuration when the RLF occurred. In certain embodiments, WD 110 may also include other information, such as whether the RLF occurred in conjunction with a BWP switch and, if so, whether the switching was caused by a DCI signal or a timer. In certain embodiments, the RFL report may also include information about the old BWP, if the RFL has occurred in conjunction with a switch from an old to a new BWP. In certain modalities, some or all of this information may be included (additionally or alternatively) in an RRC Connection Reestablishment Request.
[0183] [0183] In certain embodiments, network node 160 can configure WD 110 in one or more of the various ways described above. In addition to configuring WD 110 as described above, in certain embodiments the network node 160 can transmit different reference signals on specific resource (s). For example, network node 160 can transmit different reference signals on specific resource (s) per configured BWP. As another example, network node 160 can activate certain reference signals after activating a given BWP. For example, in certain modalities the transmission of RLM RS can be triggered by activating the BWP to at least one WD (for example, by the fact that the network node starts transmitting PDCCH in that newly activated BWP for that WD).
[0184] [0184] The following section illustrates an exemplary approach to how one or more of the modalities described above can be implemented in a standard. The description below reflects a possible approach and the present invention is not limited to the examples described below. Modifications, additions or omissions can be made to the exemplary approach described below without departing from the scope of the present invention.
[0185] [0185] There are two options for how to do RLM when there are multiple BWPs configured for a UE. A first option is to monitor the current active BWP all the time. A second option is to monitor the BWPs dedicated to the RLM. As agreed in RAN1, both SSB and CSI-RS can be configured as RLM RS. Since not all BWP can be configured with SSB however each BWP can be configured with CSI-RS, so how to do RLM can be different by RS. As agreed in RAN2, there is only one cell definition SSB in a carrier. The cell that defines SSB is considered as the time reference of the server cell and for measurements of RRM server cell based on SSB. If the SSB is configured as RLM RS, it may be beneficial to follow principles similar to those for measuring server cell RRM. That is, the cell definition SSB is used for RLM. This means that when there is no cell definition SSB in the current active BWP, a UE needs to switch to the BWP with cell definition SSB for RLM purposes. This is also the case for measuring RRM. That is, when UE needs to perform RRM measurement of server cell and the SSB is not in the active BWP, then the UE needs to switch to BWP with the cell definition SSB for RRM measurement. According to RAN1, measuring in an RS that is not in the active BWP of the UE means that a gap is necessary. Thus, for SSB-based RLM, RLM is in the BWP with cell definition SSB. RLM is carried in the measurement gap when active BWP has no cell definition SSB.
[0186] [0186] For RLM based on CSI-RS, each active BWP must be configured with CSI-RS. So it is quite natural that RLM is in the BWP active all the time. In other words, for CSI-RS-based RLM, the RLM can always be in the active BWP.
[0187] [0187] Since both SSB and CSI-RS based RLM needs to be supported, it is proposed that both active BWP RLM and designated BWP RLM should be supported and which one to choose depends on which RS is configured as RLM RS. Since SSB-based RLM does not depend on BWP, the configuration of RLM-related parameters can be at the cell level. While as CSI-RS-based RLM is dependent on BWP, the UE needs to know the CSI-RS feature to monitor on active BWP; therefore, in addition to some common parameters (for example, timers and constants that are shared by different BWP), there must be some specific BWP RLM configuration (for example, where is the CSI-RS feature to monitor). Thus, it is proposed that RLM based on CSI-RS include specific configuration of BWP and group of cells.
[0188] [0188] With respect to beam failure / recovery and RLF firing, it should be considered whether events related to beam failure can be part of it explicitly, considering the following RAN1 agreements: The NR must endeavor to provide indication (s) ) aperiodic (s) based on the beam failure recovery procedure to assist radio link failure (RLF) procedure, if the same RS is used for beam failure recovery and RLM procedures. As a first example, aperiodic indication (s) based on the beam failure recovery procedure can reset / stop T310. As a second example, aperiodic indication (s) based on the failure of the beam recovery procedure. It is for further study the use of aperiodic indication (s) based on the beam failure recovery procedure to assist the RLF procedure if different RS is used.
[0189] [0189] That is, there may be an aperiodic indication of L1 that indicates success or failure of the beam failure recovery procedure. How to use this aperiodic indication in the RLM / RLF procedure needs to be established. The beam failure and recovery procedure can be summarized as follows: The UE monitors configured DL beam (s) / pair (s) and based on that UE can detect beam failure; when detecting the failure the UE can select new beam (s) / DL pairs (which can be from the same cell or from a different cell, if configured); when selecting new beam (s) the UE triggers a beam recovery attempt by notifying the network (UL message); UE monitors a network response to finally declare a successful recovery.
[0190] [0190] Therefore, it should be useful to provide aperiodic indication (s) based on the beam failure recovery procedure to assist radio link failure (RLF) procedure, if the same RS is used for failure recovery beam and RLM procedures. It is necessary to decide whether such an aperiodic indicator can influence RLM / RLF or not and, if so, how. If it is assumed that a successful beam recovery (possibly indicated by receiving the network message on the selected beam) will lead to the generation of IS events and, once the UE starts measuring the RS used for RLM after a successful recovery , the number of IS events is likely to increase and at some point the RLF timer should be stopped due to this. However, if T310 is close to expiring when the beam recovery is successful, despite the fact that it is a matter of time to detect link recovery, the UE can declare RLF. For this reason, it can be argued that the detection of a successful recovery should immediately stop the RLF timer. However, although a successful beam recovery indicates that the link is very likely to be recovered, periodic IS events are likely to be a more secure mechanism in which the higher layers can ensure that the link is not only recovered, but also stable over time. Thus, the possibility of configuring the UE to not only interrupt the RLF timer after a successful beam recovery has occurred but also based on the periodic IS indication generated due to the beam recovery plus a number of configurable periodic IS events ( which may have a value less than the counter equivalent to N311 in LTE) should be considered. In some extreme cases, there may not be enough periodic IS events to interrupt the RLF timer even if the beam failure recovery is successful. Thus, it is proposed that successful beam recovery can be used in conjunction with periodic IS to interrupt the RLF timer.
[0191] [0191] Regarding the beam failure recovery failure, assuming this means only from the bottom layer perspective, no additional beam failure recovery procedures will continue. So it is not clear whether
[0192] [0192] In addition, an indication of success or failure in beam recovery, the attempt to recover from beam failure can also be considered for the RLM / RLF procedure. One possible scenario is that the UE detects a beam failure and starts preparing for the beam recovery, for example, selecting a new beam before submitting an associated UL recovery request. During this process, the RLF timer may be running so that while the UE is still trying to recover, an RLF can potentially be declared, despite the high potential for a successful procedure, for example, if the UE has selected a new beam that is strong enough and stable. If as proposed for the success case the UE also interrupts the RLF timer even in the recovery attempt, and the attempt is unsuccessful, it will take longer before the RLF timer starts again (i.e., based on events OOS) and the UE would be unnecessarily inaccessible for much longer. Therefore, to avoid an early stop of the RLF timer, one possibility could be to put it on hold during the recovery attempt. If the beam failure recovery is successful, proposal 1 can be applied; if, if not successful, proposal 2 can be applied. It is proposed that the beam recovery attempt can be used to put the RLF timer on hold.
[0193] [0193] In LTE, RLF modeling has two phases. The first phase occurs before the RLF timer is triggered in LTE and the second phase starts later. Among the open questions is the existence of a second phase, after the expiration of the RLF timer. In LTE, a second timer is triggered and EU-based mobility / cell reselection is allowed, before the reset is triggered.
[0194] [0194] It is proposed that when the RLF timer expires, the "Second phase" timer starts and the UE can perform UE-based mobility (ie cell reselection).
[0195] [0195] In LTE, when the RLF timer expires, the RRC connection reestablishment procedure is triggered, in which the UE performs cell reselection first. If the new selected cell is still an LTE cell, UE starts the random access procedure on that cell and then sends RRCConnectionReestablishmentRequest message towards the network. If the new cell selected is an inter-RAT cell, then UE must perform the actions when exiting RRC_CONNECTED.
[0196] [0196] In NR, an additional aspect related to the second phase that must be discussed further concerns the case in which the UE is reselected to a cell from which it was previously configured to perform beam recovery. In other words, the network can configure the UE to select a beam from the PCell after the beam failure or select a beam from another cell. After the RLF is declared, it reselects to one of these configured cells, there is no reason not to perform beam recovery for one of these cells instead of the usual RRC connection reconfiguration.
[0197] [0197] An additional aspect to consider in NR is the possibility that after the RLF the UE reselects to an LTE cell. If the new cell selected is an LTE cell that connects to the Next Generation Nucleus, we think that it is not necessary for the UE to leave the RRC_CONNECTED state and make the cell selection from scratch. The UE must also continue with the RRC reset procedure instead of leaving RRC_CONNECTED even though this new selected cell is an inter-RAT cell. This is reasonable since the UE can build its context in the LTE cell from the old NR cell since the two cells are using the same core network. If the new cell selected is an LTE cell that connects to the legacy EPC or another inter-RAT cell, then the UE must take action when leaving RRC_CONNECTED. It is proposed that when the UE finds RLF in the NR and reselects to an NR cell or an LTE cell that connects to the 5GC, the RRC connection reestablishment procedure is applied. Otherwise, the UE performs actions when exiting RRC_CONNECTED.
[0198] [0198] FIGURE 7 is a flow chart of a method 700 in a UE, according to certain modalities. Method 700 begins at step 701, in which the UE obtains one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth.
[0199] [0199] In certain embodiments, obtaining one or more radio link monitoring configurations may comprise receiving one or more radio link monitoring configurations in a message from a network node. In certain embodiments, obtaining one or more radio link monitoring configurations may comprise determining one or more radio link monitoring configurations according to one or more predefined rules.
[0200] [0200] In certain embodiments, each radio link monitoring configuration may comprise: a set of radio resources to perform radio link monitoring within its associated bandwidth portion; and one or more configuration parameters to perform radio link monitoring within its associated bandwidth portion.
[0201] [0201] In certain embodiments, the radio resource set may comprise a CSI-RS resource. In certain embodiments, the radio resource set may comprise an SSB.
[0202] [0202] In certain embodiments, the one or more configuration parameters for performing radio link monitoring within their associated bandwidth portion may comprise one or more of: one or more filtering parameters; one or more radio link failure timers; an evaluation period; a number of retransmissions before the radio link failure is declared; a hypothetical channel configuration; a hypothetical signal configuration; and a mapping function for a measured link quality and a hypothetical channel blocking error rate. In certain embodiments, the one or more configuration parameters for performing radio link monitoring within their associated bandwidth portion may comprise one or more filter parameters and the one or more filter parameters may comprise one or more of counters. N310, N311, N313 and N314. In certain embodiments, the one or more configuration parameters for performing radio link monitoring within their associated bandwidth portion may comprise one or more radio link failure timers and one or more radio link failure timers. radio can comprise one or more of T310, T311, T313 and T314 timers.
[0203] [0203] In certain embodiments, at least one of the one or more radio link monitoring configurations obtained may comprise a standard radio link monitoring configuration. In certain embodiments, the standard radio link monitoring configuration may be associated with a portion of standard bandwidth.
[0204] [0204] In step 702, the UE determines that the UE should switch from a source bandwidth portion to a destination bandwidth portion.
[0205] [0205] In step 703, the UE performs radio link monitoring in the destination bandwidth portion according to a obtained radio link monitoring configuration associated with the destination bandwidth portion.
[0206] [0206] In certain embodiments, the method may comprise monitoring a downlink channel quality of a first part of bandwidth and a second part of bandwidth. In certain embodiments, performance monitoring may comprise: estimating, during a first period of time, a radio link quality of the first part of bandwidth according to a configuration of radio link monitoring associated with the first part of width band; and estimating, over a second period of time, a radio link quality of the second part of bandwidth according to a radio link monitoring configuration associated with the second part of bandwidth, in which the second time period at least partially overlaps with the first period of time. In certain embodiments, the first bandwidth portion may comprise the source bandwidth portion and the second bandwidth portion may comprise the destination bandwidth portion. In certain embodiments, monitoring can be triggered based on an activation rate of one or more of the first part of bandwidth and the second part of bandwidth.
[0207] [0207] In certain embodiments, the radio link monitoring configuration associated with the destination bandwidth portion may comprise a plurality of sets of radio resources and the method may further comprise selecting one or more from the plurality of sets of radio resources radio resources to use to perform radio link monitoring on the target bandwidth portion based on a predefined rule.
[0208] [0208] In certain embodiments, a plurality of radio link monitoring configurations may be associated with the destination bandwidth portion and the method may further comprise receiving an instruction via downlink control information to use one of the plurality of radio link monitoring settings to perform radio link monitoring in the target bandwidth portion.
[0209] [0209] In certain embodiments, a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion may use the same radio resources and performing radio link monitoring on the target bandwidth portion according to the radio link monitoring configuration obtained associated with the destination bandwidth portion may comprise using one or more of the measurements performed previously and samples of measurements performed previously to generate events out of sync and in sync.
[0210] [0210] In certain embodiments, a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion may use different radio resources. In certain embodiments, performing radio link monitoring on the destination bandwidth portion according to the obtained radio link monitoring configuration associated with the destination bandwidth portion may comprise applying a relationship function to one or more among previously performed measurements and samples of previously performed measurements to generate out-of-sync and in-sync events without resetting a radio link failure timer or radio link failure counter. In certain embodiments, performing radio link monitoring on the destination bandwidth portion according to the radio link monitoring configuration obtained associated with the destination bandwidth portion may comprise resetting at least one of a fault timer link link and a radio link failure counter. In certain embodiments, resetting at least one of a radio link failure timer and a radio link failure counter may comprise resetting a set of radio link failure timers and radio link failure counters associated with monitoring link errors for out-of-sync events and allow a set of radio link failure timers and radio link failure counters associated with radio link monitoring for events in sync to continue. In certain embodiments, resetting at least one of a radio link failure timer and a radio link failure counter may comprise resetting one or more radio link failure timers without resetting any radio link failure counters.
[0211] [0211] FIGURE 8 is a schematic block diagram of a virtualization device, according to certain modalities. More particularly, FIGURE 8 illustrates a schematic block diagram of an apparatus 800 on a wireless network (for example, the wireless network shown in FIGURE 6). The apparatus may be implemented in a wireless device (for example, wireless device 110 shown in FIGURE 6. The apparatus 800 is operable to perform the example method described with reference to FIGURE 7 and possibly any other processes or methods disclosed herein It should also be understood that the method of FIGURE 7 is not necessarily performed only by the apparatus 800. At least some operations of the method can be performed by one or more other entities.
[0212] [0212] The Virtual Appliance 800 may comprise a set of processing circuits, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), digital logic for special purposes and the like. The processing circuitry can be configured to execute program code stored in memory, which can include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, memory devices flash memory, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols as well as instructions for carrying out one or more of the techniques described in the present invention in various modalities. In some implementations, the processing circuitry can be used to cause the receiving unit 802, determination unit 804, communication unit 806 and any other suitable units of the apparatus 800 to perform corresponding functions according to one or more modalities of the present invention.
[0213] [0213] In certain embodiments, apparatus 800 may be a UE. As shown in Figure 8, apparatus 800 includes reception unit 802, determination unit 804 and communication unit 806. Reception unit 802 can be configured to perform the reception functions of the device
[0214] [0214] With another example, in certain embodiments, a plurality of radio link monitoring configurations can be associated with the destination bandwidth portion and the 802 receiving unit can be configured to receive an instruction via downlink control information to use one of the plurality of radio link monitoring configurations to perform radio link monitoring on the destination bandwidth portion.
[0215] [0215] 802 receiving unit can receive any suitable information (for example, from a wireless device or other network node). Receiving unit 802 may include a receiver and / or a transceiver, such as RF transceiver circuitry 122 described above in relation to FIGURE 6. 802 receiving unit may include circuitry configured to receive messages and / or signals (wirelessly or wired). In particular embodiments, the receiving unit 802 may communicate messages and / or signals received to the determining unit 804 and / or any other suitable unit of apparatus 800. The functions of the receiving unit 802 may, in certain embodiments, be performed on one or more more separate units.
[0216] [0216] Determination unit 804 can perform the processing functions of device 800. For example, determination unit 804 can be configured to obtain one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least part of the bandwidth. In certain embodiments, determination unit 804 can be configured to determine one or more radio link monitoring configurations according to one or more predefined rules. As another example, determination unit 804 can be configured to determine that the UE should switch from a source bandwidth portion to a destination bandwidth portion.
[0217] [0217] As yet another example, determination unit 804 can be configured to perform radio link monitoring on the target bandwidth portion according to a obtained radio link monitoring configuration associated with the bandwidth portion. destiny. In certain embodiments, determination unit 804 can be configured to perform a downlink channel quality monitoring of a first part of bandwidth and a second part of bandwidth. In certain embodiments, the receiving unit 804 can be configured to estimate, over a first period of time, a radio link quality of the first part of bandwidth according to a radio link monitoring configuration associated with the first part of bandwidth; and estimating, over a second period of time, a radio link quality of the second part of bandwidth according to a radio link monitoring configuration associated with the second part of bandwidth, in which the second time period at least partially overlaps with the first period of time.
[0218] [0218] As yet another example, in certain embodiments the radio link monitoring configuration associated with the destination bandwidth portion may comprise a plurality of radio resource sets, and determination unit 804 may be configured to select one or more from the plurality of radio resource sets to use to perform radio link monitoring in the destination bandwidth portion based on a predefined rule.
[0219] [0219] As another example, in certain embodiments, a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with a destination bandwidth portion may use the same radio resources and determination unit 804 can be configured to use one or more of the measurements performed previously and samples of measurements performed previously to generate events out of sync and in sync.
[0220] [0220] As another example, in certain embodiments, a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion may use radio resources different and perform radio link monitoring on the target bandwidth portion according to the obtained radio link monitoring configuration associated with the destination bandwidth portion, determination unit 804 can be configured to apply a function with respect to one or more of the measurements performed previously and samples of measurements performed previously to generate events out of sync and in sync without resetting a radio link failure timer or radio link failure counter. In certain embodiments, determination unit 804 can be configured to reset at least one of a radio link failure timer and a radio link failure counter. In certain embodiments, determination unit 804 can be configured to reset a set of radio link failure timers and radio link failure counters associated with radio link monitoring for out-of-sync events and allow a set of radio link timers. radio link failure and radio link failure counters associated with radio link monitoring so that events in sync continue. In certain embodiments, determination unit 804 can be configured to reset one or more radio link failure timers without resetting any radio link failure counters.
[0221] [0221] Determination unit 804 can include or be included in one or more processors, such as the processing circuitry 120 described above in relation to FIGURE 6. The determination unit 804 can include analog and / or digital circuitry configured to perform any of the functions of determination unit 804 and / or processing circuitry 120 described above. Determination unit functions 804 may, in certain embodiments, be performed in one or more separate units.
[0222] [0222] Communication unit 806 can be configured to perform the transmission functions of device 800. Communication unit 806 can transmit messages (for example, to a wireless device and / or another network node). Communication unit 806 may include a transmitter and / or a transceiver, such as RF transceiver circuitry 122 described above with reference to FIGURE 6. Communication unit 806 may include circuitry configured to transmit messages and / or signals (for example , wirelessly or wired). In particular embodiments, communication unit 806 can receive messages and / or signals for transmission from determination unit 804 or any other device unit 800. The functions of communication unit 804 can, in certain modalities, be performed in one or more more separate units.
[0223] [0223] The term unit may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, a set of electrical and / or electronic circuits, devices, modules, processors, memories, logical solid state and / or discrete devices, computer programs or instructions for performing the respective tasks, procedures, computations, outputs and / or displaying functions and so on, such as those described in the present invention.
[0224] [0224] FIGURE 9 is a flow chart of a 900 method on a network node, according to certain modalities. Method 900 begins at step 901, where the network node determines one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of the bandwidth.
[0225] [0225] In certain embodiments, each radio link monitoring configuration may comprise a set of radio resources to perform radio link monitoring within its associated bandwidth portion and one or more configuration parameters to perform radio monitoring. radio link within its associated bandwidth portion. In certain embodiments, the radio resource set may comprise a CSI-RS resource. In certain embodiments, the radio resource set may comprise an SSB.
[0226] [0226] In certain embodiments, the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more of: one or more filtering parameters; one or more radio link failure timers; an evaluation period; a number of retransmissions before the radio link failure is declared; a hypothetical channel configuration; a hypothetical signal configuration; and a mapping function for a measured link quality and a hypothetical channel blocking error rate. In certain embodiments, the one or more configuration parameters for performing radio link monitoring within their associated bandwidth portion may comprise one or more filter parameters and the one or more filter parameters may comprise one or more of counters. N310, N311, N313 and N314. In certain embodiments, the one or more configuration parameters for performing radio link monitoring within their associated bandwidth portion may comprise one or more radio link failure timers and one or more radio link failure timers. radio can comprise one or more of T310, T311, T313 and T314 timers.
[0227] [0227] In certain embodiments, at least one of the one or more radio link monitoring configurations determined may comprise a standard radio link monitoring configuration. In certain embodiments, the standard radio link monitoring configuration may be associated with a portion of standard bandwidth.
[0228] [0228] In step 902, the network node configures a UE to perform radio link monitoring on a destination bandwidth portion according to a radio link monitoring configuration associated with the destination bandwidth portion .
[0229] [0229] In certain embodiments, configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion may comprise sending an indication the radio link monitoring configuration associated with the destination bandwidth portion for the UE. In certain embodiments, sending the indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE may comprise sending an indication of the radio link monitoring configuration associated with the destination bandwidth portion in an information element within a bandwidth portion setting for the destination bandwidth portion. In certain embodiments, sending the indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE may comprise sending an indication of the radio link monitoring configuration associated with the destination bandwidth portion on a information element within a server cell configuration. In certain embodiments, the indication may comprise a radio link monitoring configuration identifier.
[0230] [0230] In certain embodiments, configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion may comprise configuring the UE to determine the radio link monitoring configuration associated with the destination bandwidth portion according to one or more predefined rules.
[0231] [0231] In certain embodiments, the radio link monitoring configuration associated with the destination bandwidth portion may comprise a plurality of sets of radio resources and the method may further comprise configuring the UE to select one or more from among plurality of sets of radio resources to use to perform radio link monitoring in the target bandwidth portion based on a predefined rule.
[0232] [0232] In certain embodiments, a plurality of radio link monitoring configurations may be associated with the destination bandwidth portion and the method may additionally comprise sending an instruction to the UE to use one of the plurality of monitoring configurations radio link to perform radio link monitoring on the destination bandwidth portion.
[0233] [0233] In certain embodiments, a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with a destination bandwidth portion may use the same radio resources and configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion that can comprise the configuration of the UE to use one or more more of the measurements performed previously and samples of measurements performed previously to generate out-of-sync and in-sync events.
[0234] [0234] In certain embodiments, a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with a destination bandwidth portion may use different radio resources.
[0235] [0235] FIGURE 10 is a schematic block diagram of a virtualization device, according to certain modalities. More particularly, FIGURE 10 illustrates a schematic block diagram of an apparatus 1000 on a wireless network (for example, the wireless network shown in FIGURE 6). The apparatus can be implemented on a network node (for example, network node 160 shown in FIGURE 6). Apparatus 1000 is operable to carry out the example method described with reference to FIGURE 9 and possibly any other processes or methods disclosed in the present invention. It should also be understood that the method of FIGURE 9 is not necessarily performed only by the device 1000. At least some operations of the method can be performed by one or more other entities.
[0236] [0236] The Virtual Appliance 1000 may comprise a set of processing circuits, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), digital logic for special purposes and the like. The processing circuitry can be configured to execute program code stored in memory, which can include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, memory devices flash memory, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols as well as instructions for carrying out one or more of the techniques described in the present invention in various modalities. In some implementations, the processing circuitry can be used to cause the receiving unit 1002, determination unit 1004, communication unit 1006 and any other suitable units of the apparatus 1000 to perform corresponding functions according to one or more modalities of the present invention.
[0237] [0237] In certain embodiments, apparatus 1000 can be an eNB or a gNB. As illustrated in FIGURE 10, apparatus 1000 includes receiving unit 1002, determining unit 1004 and communication unit 1006. Receiving unit 1002 can be configured to perform the functions of receiving apparatus 1000. Receiving unit 1002 can receive any suitable information (for example, from a wireless device or other network node). Receiving unit 1002 can include a receiver and / or a transceiver, such as RF transceiver circuitry 172 described above with reference to FIGURE 6. Receiving unit 1002 can include circuitry configured to receive messages and / or signals (wirelessly or wired). In particular embodiments, the receiving unit 1002 can communicate messages and / or signals received to the determining unit 1004 and / or any other suitable apparatus unit 1000. The functions of the receiving unit 1002 can, in certain embodiments, be performed on one or more more separate units.
[0238] [0238] Determination unit 1004 can perform the processing functions of device 1000. For example, determination unit 1004 can be configured to determine one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least part of the bandwidth. As another example, determination unit 1004 can be configured to configure a UE to perform radio link monitoring on a target bandwidth portion according to a radio link monitoring configuration associated with the bandwidth portion. destiny.
[0239] [0239] Determination unit 1004 can include or be included in one or more processors, such as the processing circuitry 170 described above in relation to FIGURE 6. Determination unit 1004 can include analog and / or digital circuitry configured to perform any of the functions of determination unit 1004 and / or processing circuit set 170 described above. Determination unit functions 1004 can, in certain embodiments, be performed in one or more separate units.
[0240] [0240] Communication unit 1006 can be configured to perform the transmission functions of device 1000. For example, in certain embodiments, a plurality of radio link monitoring configurations can be associated with the destination bandwidth portion and unit of communication. communication 1006 can be configured to send an instruction to the UE to use one of the plurality of radio link monitoring configurations to perform radio link monitoring on the destination bandwidth portion. As another example, communication unit 1006 can be configured to send an indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE. In certain embodiments, communication unit 1006 can be configured to send an indication of the radio link monitoring configuration associated with the destination bandwidth portion in an information element within a portion of the bandwidth portion destination bandwidth. In certain embodiments, communication unit 1006 can be configured to send an indication of the radio link monitoring configuration associated with the destination bandwidth portion of an information element within a server cell configuration.
[0241] [0241] Communication unit 1006 can transmit messages (for example, to a wireless device and / or another network node). Communication unit 1006 may include a transmitter and / or transceiver, such as the RF 172 transceiver circuitry described above with reference to FIGURE
[0242] [0242] The term unit may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, a set of electrical and / or electronic circuits, devices, modules, processors, memories, logical solid state and / or discrete devices,
[0243] [0243] FIGURE 11 illustrates a modality of a UE, according to certain modalities. As used in the present invention, user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operated by, a human user, but that cannot, or may not be initially associated with, a specific human user. A UE can also understand any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE that is not intended for sale to, or operation by, a human user. The UE 1100, as illustrated in FIGURE 11, is an example of a WD configured for communication according to one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE standards and / or 5G. As mentioned earlier, the term WD and UE can be used interchangeably. Therefore, although FIGURE 11 is a UE, the components discussed in the present invention are equally applicable to a WD and vice versa.
[0244] [0244] In FIGURE 11, UE 1100 includes a set of processing circuits 1101 that is operationally coupled to the input / output interface 1105, radio frequency (RF) interface 1109, network connection interface 1111, memory 1115 including access memory random (RAM) 1117, read-only memory (ROM) 1119 and storage medium 1121 or similar, communication subsystem 1131, power source 1113 and / or any other component or any combination thereof. Storage medium 1121 includes operating system 1123, application program 1125 and data 1127. In other embodiments, storage medium 1121 may include other similar types of information. Certain UEs can use all the components shown in FIGURE 11 or only a subset of the components. The level of integration between the components can vary from one UE to another UE. In addition, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0245] [0245] In FIGURE 11, processing circuitry 1101 can be configured to process instructions and computer data. Processing circuitry 1101 can be configured to implement any sequential operating state machine to execute machine instructions stored as machine-readable computer programs in memory, such as one or more hardware-implemented state machines (for example, in discrete logic, FPGA, ASIC etc.); programmable logic along with the appropriate firmware; one or more stored programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), along with appropriate software; or any combination of the above. For example, processing circuitry 1101 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.
[0246] [0246] In the represented mode, the input / output interface 1105 can be configured to provide a communication interface for an input device, output device or input and output device. The UE 1100 can be configured to use an output device via the input / output interface 1105. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input and output to the UE 1100. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator , an issuer, a smartcard, another output device, or any combination thereof. The UE 1100 can be configured to use an input device via the 1105 input / output interface to allow a user to capture information on the UE
[0247] [0247] In FIGURE 11, RF interface 1109 can be configured to provide a communication interface for RF components such as a transmitter, receiver and antenna. The 1111 network connection interface can be configured to provide a communication interface for the 1143a network. Network 1143a can encompass wired and / or wireless networks such as a local area network (LAN), a geographically distributed network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination of them. For example, network 1143a can comprise a Wi-Fi network. The network connection interface 1111 can be configured to include a receiving interface and a transmitter used to communicate with one or more other devices over a communication network in accordance with one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM or the like. The 1111 network connection interface can implement the appropriate receiver and transmitter functionality for communication network links (for example, optical, electrical and the like). The transmitter and receiver functions can share circuit, software or firmware components or alternatively they can be implemented separately.
[0248] [0248] RAM 1117 can be configured to interface via bus 1102 to processing circuitry 1101 to provide storage or caching of data or computer instructions during the execution of software programs, such as the operating system, application programs and device drivers. ROM 1119 can be configured to provide instructions or computer data for 1101. processing circuitry. For example, ROM 1119 can be configured to store invariable low-level system data or codes for basic system functions such as basic input and output (I / O), initialization or reception of keystrokes on a keyboard that are stored in a non-volatile memory. The 1121 storage medium can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, disks optical drives, floppy disks, hard drives, removable cartridges or flash drives. In one example, storage medium 1121 can be configured to include the operating system 1123, the application program 1125 such as a web browser application, a widget or gadget mechanism or other application and data file
[0249] [0249] Storage medium 1121 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy drive, flash memory, USB flash drive, external hard drive, thumb drive , flash drive, Key drive, versatile high-density digital disk (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disk drive, holographic digital data storage optical disk drive (HDDS) ), external mini in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro SDRAM DIMM, smartcard memory, as a subscriber identity module or a removable user identity module ( YES / BAD) another memory or any combination thereof. The storage medium 1121 can allow the UE 1100 to access executable instructions by computer, application programs or the like, stored on transient or non-transient memory media, to download data or upload data. An article of manufacture, such as one using a communication system, can be tangibly incorporated into the storage medium 1121, which can comprise a device-readable medium.
[0250] [0250] In FIGURE 11, the processing circuitry 1101 can be configured to communicate with network 1143b using communication subsystem 1131. Network 1143a and network 1143b can be the same network or networks or different networks or network. The 1131 communication subsystem can be configured to include one or more transceivers used to communicate with the 1143b network. For example, communication subsystem 1131 can be configured to include one or more transceivers used to communicate with one or more remote transceivers from another device capable of wireless communication such as another WD, UE or base station on a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax or the like. Each transceiver may include transmitter 1133 and / or receiver 1135 to implement transmitter or receiver functionality, respectively, appropriate for RAN links (for example, frequency allocations and the like). In addition, transmitter 1133 and receiver 1135 for each transceiver can share circuit, software or firmware components or, alternatively, can be implemented separately.
[0251] [0251] In the illustrated embodiment, the communication functions of the 1131 communication subsystem may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, proximity communication in the field, location-based communication such as use of the global positioning system (GPS) to determine a location, other similar communication function or any combination thereof. For example, the 1131 communication subsystem can include cellular communication, Wi-Fi communication, Bluetooth communication and GPS communication. Network 1143b can encompass wired and / or wireless networks such as a local area network (LAN), a geographically distributed network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination of them. For example, the 1143b network can be a cellular network, a Wi-Fi network and / or a field proximity network. The 1113 power source can be configured to provide alternating current (AC) or direct current (DC) power to the UE 1100 components.
[0252] [0252] The features, benefits and / or functions described in the present invention can be implemented in one of the components of UE 1100 or partitioned through multiple components of UE 1100. In addition, the characteristics, benefits and / or functions described in the present invention can be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1131 can be configured to include any of the components described in the present invention. In addition, processing circuitry 1101 can be configured to communicate with any of these components via bus 1102. In another example, any of these components can be represented by program instructions stored in memory which, when executed by the assembly of processing circuits 1101 perform the corresponding functions described in the present invention. In another example, the functionality of any of these components can be partitioned between the processing circuitry 1101 and the communication subsystem 1131. In another example, the non-computationally intensive functions of any of these components can be implemented in software or firmware and computationally intensive functions can be implemented in hardware.
[0253] [0253] FIGURE 12 is a schematic block diagram that illustrates a virtualization environment, according to certain modalities. More particularly, FIGURE 12 is a schematic block diagram illustrating a virtualization environment 1200 in which functions implemented by some modalities can be virtualized. In the present context, virtualizing means creating virtual versions of devices or devices which can include virtualization hardware platforms, storage devices and network resources. As used in the present invention, virtualization can be applied to a node (for example, a virtualized base station or a virtualized radio access node) or to a device (for example, a UE, a wireless device or any other type communication device) or components thereof and refers to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (for example, through one or more applications, components, functions, virtual machines or containers running on one or more physical processing nodes on one or more networks).
[0254] [0254] In some embodiments, some or all of the functions described in the present invention can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more hardware nodes 1230. In addition, in the modalities in which the virtual node is not a radio access node or does not require radio connectivity (for example, a core network node), then the network node can be fully virtualized.
[0255] [0255] The functions can be implemented by one or more 1220 applications (which can alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions etc.) operating to implement some of the features, functions and / or benefits of some of the embodiments disclosed in the present invention. Applications 1220 are run in the virtualization environment 1200, which provides hardware 1230 comprising a set of processing circuits 1260 and memory 1290. Memory 1290 contains instructions 1295 executable by the set of processing circuits 1260 whereby application 1220 is operative to provide one or more of the features, benefits and / or functions disclosed in the present invention.
[0256] [0256] Virtualization environment 1200 comprises general-purpose or special-purpose network hardware devices 1230 comprising a set of one or more processors or 1260 processing circuitry, which may be commercial off-the-shelf (COTS) processors, Circuits Dedicated Application Specific Integrated (ASICs) or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can comprise 1290-1 memory which can be non-persistent memory to temporarily store 1295 instructions or software executed by the 1260 processing circuitry. Each hardware device can comprise one or more network interface controllers (NICs) 1270, also known as network interface cards, which include 1280 physical network interface. Each hardware device can also include non-transient, persistent and machine-readable 1290-2 storage media, having stored in software 1295 and / or instructions executable by the 1260 processing circuitry. The 1295 software can include any type of software, including software to instantiate one or more 1250 virtualization layers (also called hypervisors), software to run 1240 virtual machines as well as software to run functions, characteristics and / or benefits described in relation to any the modalities described in the present invention.
[0257] [0257] 1240 virtual machines comprise virtual processing, virtual memory, virtual network or interface and virtual storage and can be performed by a corresponding virtualization layer 1250 or hypervisor. Different modalities of the 1220 virtual appliance instance can be implemented on one or more 1240 virtual machines and the implementations can be done in different ways.
[0258] [0258] During operation, the processing circuitry 1260 runs software 1295 to instantiate the hypervisor or virtualization layer 1250, which can sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 1250 can feature a virtual operating platform that appears as network hardware for the virtual machine
[0259] [0259] As shown in FIGURE 12, hardware 1230 can be an autonomous network node with generic or specific components. The 1230 hardware can comprise the 12225 antenna and can implement some functions via virtualization. Alternatively, 1230 hardware can be part of a larger hardware cluster (for example, such as in a data center or equipment within the customer's facilities (CPE)) where many hardware nodes work together and are managed through Management and Orchestration (MANO) 12100, which, among others, supervises the 1220 application lifecycle management.
[0260] [0260] Hardware virtualization is in some contexts called network function virtualization (NFV). NFV can be used to consolidate many types of network equipment into industry-standard high-volume server hardware, physical switches and physical storage, which can be located in data centers and equipment within the customer's facilities.
[0261] [0261] In the context of NFV, virtual machine 1240 can be a software implementation of a physical machine that runs programs as if they were running on a non-virtualized physical machine. Each of the 1240 virtual machines and that piece of hardware 1230 that runs that virtual machine, whether the hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other 1240 virtual machines, form separate virtual network elements (VNE).
[0262] [0262] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run on one or more virtual machines 1240 on top of the hardware network infrastructure 1230 and corresponds to application 1220 on FIGURE 12.
[0263] [0263] In some embodiments, one or more 12200 radio units that each include one or more 12220 transmitters and one or more 12210 receivers can be coupled to one or more 12225 antennas. The 12200 radio units can communicate directly with the 1230 hardware nodes via one or more appropriate network interfaces and can be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
[0264] [0264] In some modalities, some signaling can be done using the 12230 control system that can be used alternatively for communication between hardware nodes 1230 and radio units 12200.
[0265] [0265] FIGURE 13 illustrates an example telecommunications network connected via an intermediate network to a host computer, according to certain modalities. With reference to FIGURE 13, according to one modality, a communication system includes a telecommunications network 1310, such as a cellular network of the 3GPP type, comprising access network 1311, such as a radio access network and a core network 1314. A Access network 1311 comprises a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c can be connected to the core network 1314 via a wired or wireless connection 1315. A first UE 1391 located in the coverage area
[0266] [0266] The 1310 telecommunications network itself is connected to the host computer 1330, which can be incorporated into the hardware and / or software of a stand-alone server, a server deployed in the cloud, a distributed server or as processing resources on a server farm . The 1330 host computer may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 1321 and 1322 between the telecommunications network 1310 and the host computer 1330 can extend directly from the core network 1314 to the host computer 1330 or can pass via an optional intermediate network 1320. The intermediate network 1320 can be one of, or a combination of more than one of a public, private or hosted network; intermediate network 1320, if any, can be a backbone network or the Internet; in particular, intermediate network 1320 may comprise two or more subnets (not shown).
[0267] [0267] The communication system of FIGURE 13 as a whole allows connectivity between the connected UEs 1391, 1392 and the host computer 1330. Connectivity can be described as an Over-the-Top (OTT) 1350 connection. Host computer 1330 and the connected UEs 1391, 1392 are configured to communicate data and / or signaling via OTT connection 1350, using access network 1311, core network 1314, any intermediate network 1320 and possible additional infrastructure (not shown) as intermediaries. The OTT 1350 connection can be transparent in the sense that the participating communication devices through which the OTT 1350 connection passes are unaware of the UL and DL communications routing. For example, base station 1312 may not be or need not be informed about the past routing of a downlink communication received with data originating from host computer 1330 to be forwarded (for example, handed over) to a connected UE 1391 . Similarly, base station 1312 need not be aware of the future routing of an outgoing UL communication from UE 1391 towards host computer 1330.
[0268] [0268] FIGURE 14 illustrates an example of a host computer communicating via a base station with a UE through a wireless connection partially, according to certain modalities. Examples of implementations, according to a modality, of the UE, base station and host computer discussed in the previous paragraphs will now be described with reference to FIGURE 14. In communication system 1400, host computer 1410 comprises hardware 1415, including communication interface 1416 configured to define and maintain a wired or wireless connection to an interface of a communication device other than the communication system 1400. The host computer 1410 additionally comprises a set of processing circuits 1418, which may have storage and / or processing capabilities . In particular, the processing circuitry 1418 may comprise one or more programmable processors, application-specific integrated circuits, field programmable port arrangements or combinations thereof (not shown) adapted to execute instructions. Host computer 1410 additionally comprises software 1411, which is stored or accessible by host computer 1410 and executable by processing circuitry 1418. Software 1411 includes host application 1412. Host application 1412 may be operable to provide a service to a remote user, such as UE 1430 connecting via an OTT 1450 connection ending at UE 1430 and host computer 1410. In providing service to the remote user, host application 1412 can provide user data which is transmitted using the OTT connection 1450.
[0269] [0269] The communication system 1400 additionally includes base station 1420 provided in a telecommunications system and comprising hardware 1425 allowing it to communicate with the host computer 1410 and the UE 1430. Hardware 1425 may include the communication interface 1426 for define and maintain a wired or wireless connection with a communication device interface other than the 1400 communication system, as well as the radio interface 1427 to define and maintain at least 1470 wireless connection with UE 1430 located in a coverage area (not shown in FIGURE 14) served by base station 1420. Communication interface 1426 can be configured to facilitate connection 1460 to host computer 1410. Connection 1460 can be direct, or it can pass through a core network (not explicitly shown in FIGURE 14) of the telecommunications system and / or through one or more intermediary networks outside the telecommunications system. In the embodiments shown, the hardware 1425 of the base station 1420 additionally includes a set of processing circuits 1428, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable port arrangements or combinations thereof (not shown) adapted to execute instructions. The base station 1420 also has software 1421 stored internally or accessible via an external connection.
[0270] [0270] The communication system 1400 additionally includes the UE 1430 already mentioned. Your 1435 hardware may include a radio interface 1437 configured to define and maintain the wireless connection 1470 with a base station that serves a coverage area in which the UE 1430 is currently located. The 1435 hardware of the UE 1430 additionally includes a set of 1438 processing circuits, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable port arrangements or combinations thereof (not shown) adapted to execute instructions. The UE 1430 additionally comprises software 1431 stored or accessible by the UE 1430 and executable by the processing circuitry 1438. The software 1431 includes the client application 1432. The client application 1432 can be operable to provide a service to a human or non-human user via UE 1430, with host computer support 1410. On host computer 1410, a running host application 1412 can communicate with client application 1432 running via OTT connection 1450 terminating at UE 1430 and host computer 1410. By providing the user service, client application 1432 can receive request data from host application 1412 and provide user data in response to request data. The OTT 1450 connection can transfer both request data and user data. The 1432 client application can interact with the user to generate the user data it provides.
[0271] [0271] Note that host computer 1410, base station 1420 and UE 1430 illustrated in FIGURE 14 can be similar or identical to host computer 1330, one of base stations 1312a, 1312b, 1312c and one of UEs 1391, 1392 of FIGURE 13, respectively. That is, the internal functioning of these entities can be as shown in FIGURE 14 and, independently, the surrounding network topology can be that of FIGURE 13.
[0272] [0272] In FIGURE 14, the OTT connection 1450 was designed abstractly to illustrate the communication between host computer 1410 and UE 1430 via base station 1420, without explicit reference to any intermediate devices and the precise routing of messages via those devices. The network infrastructure can determine routing, which can be configured to hide from the UE 1430, or from the service provider operating host computer 1410, or both. While the OTT 1450 connection is active, the network infrastructure can additionally make decisions by dynamically changing routing (for example, based on consideration of load balancing or network reconfiguration).
[0273] [0273] The wireless connection 1470 between the UE 1430 and the base station 1420 is in accordance with the teachings of the modalities described throughout this invention. One or more of the various modalities improves the performance of the OTT services provided to the UE 1430 using the OTT 1450 connection, in which the wireless connection 1470 forms the last segment. More precisely, the teachings of these modalities can improve power consumption and thus provide benefits such as extended battery life and reduced user standby time.
[0274] [0274] A measurement procedure can be provided for the purpose of monitoring data rate, latency and other factors improved by one or more modalities. In addition, there may be optional network functionality to reconfigure the OTT 1450 connection between host computer 1410 and UE 1430, in response to variations in measurement results. The measurement procedure and / or network functionality for reconfiguring the OTT connection 1450 can be implemented in software 1411 and hardware 1415 of host computer 1410, in software 1431 and hardware 1435 of UE 1430 or both. In the modalities, the sensors (not shown) can be implanted in or in association with communication devices through which the OTT connection
[0275] [0275] FIGURE 15 is a flow chart of a method implemented in a communication system, according to certain modalities. The communication system includes a host computer, a base station and a UE which can be those described with reference to FIGURES 13 and 14. To simplify the present invention, only drawing references to FIGURE 15 will be included in this section. In step 1510, the host computer provides the user data. In substep 1511 (which may be optional) of step 1510, the host computer provides user data running a host application. In step 1520, the host computer initiates a transmission by carrying user data to the UE. In step 1530 (which can be optional), the base station transmits to the UE the user data that was loaded in the transmission that the host computer started, according to the teachings of the modalities described throughout this invention. In step 1540 (which can also be optional), the UE runs a client application associated with the host application run by the host computer.
[0276] [0276] FIGURE 16 is a flow chart of a method implemented in a communication system, according to certain modalities. The communication system includes a host computer, a base station and a UE that can be those described with reference to FIGURES 13 and 14. To simplify the present invention, only drawing references to FIGURE 16 will be included in this section. In step 1610 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides user data running a host application. In step 1620, the host computer initiates a transmission by porting user data to the UE. The transmission can pass via the base station, according to the teachings of the modalities described throughout this invention. In step 1630 (which can be optional), the UE receives the user data loaded in the transmission.
[0277] [0277] FIGURE 17 is a flow chart of a method implemented in a communication system, according to certain modalities. The communication system includes a host computer, a base station and a UE which can be those described with reference to FIGURES 13 and 14. To simplify the present invention, only drawing references to FIGURE 17 will be included in this section. In step 1710 (which can be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data. In substep 1721 (which can be optional) of step 1720, the UE provides user data running a client application. In substep 1711 (which may be optional) of step 1710, the UE runs a client application that provides user data in response to incoming data received and provided by the host computer. When providing user data, the executed client application can additionally consider the user input received from the user. Regardless of the specific way in which the user data was provided, the UE initiates, in substep 1730 (which may be optional), transmission of the user data to the host computer. In step 1740 of the method, the host computer receives user data transmitted from the UE, in accordance with the teachings of the modalities described throughout this invention.
[0278] [0278] FIGURE 18 is a flow chart of a method implemented in a communication system, according to certain modalities. The communication system includes a host computer, a base station and a UE which can be those described with reference to FIGURES 13 and 14. To simplify the present invention, only drawing references to FIGURE 18 will be included in this section. In step 1810 (which can be optional), according to the teachings of the modalities described throughout this invention, the base station receives user data from the UE. In step 1820 (which can be optional), the base station starts transmitting the received user data to the host computer. In step 1830 (which can be optional), the host computer receives user data ported in the transmission initiated by the base station.
[0279] [0279] Any appropriate steps, methods, characteristics, functions or benefits disclosed in the present invention can be performed through one or more functional units or modules of one or more virtual appliances. Each virtual appliance can comprise a number of these functional units. These functional units can be implemented via a set of processing circuits, which can include one or more microprocessors or microcontrollers, as well as other digital hardware, which can include digital signal processors (DSPs), digital logic for specific purposes and the like. The processing circuitry can be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for performing one or more of the techniques described in the present invention. In some implementations, the set of processing circuits can be used to make the respective functional unit perform corresponding functions in accordance with one or more embodiments of the present invention.
[0280] [0280] Modifications, additions or omissions can be made to the systems and devices described in the present invention without departing from the scope of the invention. The components of the systems and devices can be integrated or separated. In addition, system and device operations can be performed by more, less or other components. In addition, system and device operations can be performed using any suitable logic including software, hardware and / or other logic. As used in this document, "each" refers to each member of a set or each member of a subset of a set.
[0281] [0281] Modifications, additions or omissions can be made to the methods described in the present invention without departing from the scope of the invention. The methods can include more, less or other steps. In addition, the steps can be performed in any appropriate order.
[0282] [0282] Although this invention has been described in terms of certain modalities, changes and permutations of the modalities will be apparent to those skilled in the art. Therefore, the above description of the modalities does not restrict that invention. Other changes, substitutions and alterations are possible without departing from the spirit and scope of this invention, as defined by the following claims.
[0283] [0283] At least some of the following abbreviations can be used in this invention. In case of inconsistency between abbreviations, preference should be given to the one as used above. If listed multiple times below, the first listing should be preferred over any subsequent listing (s). 1x RTT CDMA2000 1x 3GPP Radio Transmission Technology 3rd Generation 5G Partnership 5th Generation ABS Almost Blank Subframe ARQ Automatic Repeat Request ASN.1 Notation for Abstract Syntax One AWGN White Gaussian Noise BCCH Diffusion Control Channel BCH BLER Diffusion Channel BWP Block Error Rate AC Bandwidth Part CC Carrier Aggregation CCCH SDU Carrier Component Common Control Channel SDU CDMA Multiple Access by CGI Code Division Global CIR Cell Identifier CORESET Channel Impulse Response Set Control Resources CP Cyclic Prefix CPICH Common Pilot Channel
CPICH Ec / No Energy received from CPICH per chip divided by the power density in the CQI band C-RNTI Channel Quality Information RNTI CRS Cell CSI Cell Specific Reference Signal CSI-RS Channel State Information Reference Information Signal DCCH Channel State DCI Dedicated Control Channel DL Downlink Control Information DM Downlink DM Demodulation Reference Signal DRB Data Radio Transporter DRX Discontinuous Reception DTX Discontinuous Transmission DTCH DUTCH Dedicated Traffic Channel Device Under Test E-CID Enhanced Cell ID (positioning method) E-SMLC Evolved Mobile Location Center E-UTRAN Evolved Universal Terrestrial Radio Access Network Evolved ECGI CGI eNB E-UTRAN Node B ePDCCH Enhanced Physical Downlink Control Channel E -SMLC Mobile Location Center Evolved Server E-UTRA UTRA Evolved E-UTRAN UTRAN Evolved FDD Duplexing by Fr Division FFS equence for additional study GERAN GSM Radio Access Network EDGE gNB NR base station
GNSS Global Navigation Satellite System GSM Global System for Mobile Communications HARQ Hybrid Auto Replay Request HO Handover HSPA High Speed Packet Access HRPD High Rate Packet Data IE IoT Information Element Internet of Things IS In Sync L1 Layer 1 L2 Layer 2 LOS Line of sight LPP Positioning Protocol LTE LTE Long Term Evolution MAC Media Access Control MBMS Multicast Multimedia Broadcast Services MBSFN Single Frequency Network Multicast Broadcast Multimedia MBSFN ABS Subframe Almost Blank MBSFN MCG Group Cellular Master MDT MIB Drive Test Minimization Information Block MME Master Mobility Management Entity MSC NB-IoT NB-IoT Narrowband NB-IoT Narrowband Internet of Things NPDCCH Narrowband Physical Downlink Control Channel NR New Radio NW OCNG Network OFDMA Channel Noise Generator
OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OOS Out of Sync OSS Operations Support System OTDOA Observed Arrival Time Difference O&M Operation and Maintenance PBCH Physical Diffusion Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Channel Physical Control Format Indicator PCI Physical Cell Identity PDCCH Physical Downlink Control Channel PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel PGW PHICH Packet Gateway PHY Physical Hybrid ARCH Indicator PLMN Physical Layer Public Terrestrial Mobile Network PMI Pre-encoding Matrix Indicator PRACH Physical Random Access Channel PRB Physical Resource Block PRS Positioning Reference Signal PSCell Primary Secondary Cell PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Channel Shared Link Ascendent and Physical QAM RACH Quadrature Amplitude Modulation RAN Random Access Channel Radio Access Network RAT Radio Access Technology
RE RLC Resource Element RLF Radio Link Control RLM Radio Link Failure RNC Radio Link Monitoring RNTI Radio Network Controller RRC Radio Network Temporary Identifier RRH Radio Resource Control RRM Remote Radio Head Resource Management Radio RRU Remote Radio Unit RS Reference Signal RSCP Signal Code Power Received RSRP Power Received from Reference Symbol OR Power Received from Reference Signal RSRQ Quality Received from Reference Signal OR Quality Received from Reference Symbol RSSI Intensity Indicator Signal Received RSTD Reference Time Difference SCH Sync Channel SCell Secondary Cell SCG Secondary Cell Group SDU Service Data Unit SFN System Frame Number SGW Gateway SI Server System Information SIB System Information Block SINR Relation Signal Interference plus Noise SNR Signal-to-Noise Ratio Auto Optimized Network SRB Tr Radio Signaling SS Synchronization Signal
SSB SS Block SSS Secondary Synchronization Signal TDD Duplexing by Time Division TDOA Arrival Time Difference TOA Arrival Time TSS Tertiary Synchronization Signal TTI Transmission Time Range EU User Equipment UL Uplink UMTS Mobile Telecommunications System Universal UP USIM User Plan UTDOA Universal Subscriber Identity Module UTRA Uplink Inbound Time Difference Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA CDMA Wide WD Wireless Device WLAN Wireless Local Area Network

权利要求:
Claims (88)
[1]
1. A method on user equipment (UE) (110), comprising: obtaining (701) one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of the band; determining (702) that the UE should switch from a source bandwidth portion to a destination bandwidth portion; and performing (703) the radio link monitoring in the destination bandwidth portion according to a obtained radio link monitoring configuration associated with the destination bandwidth portion.
[2]
The method of Claim 1, wherein obtaining one or more radio link monitoring configurations comprises receiving one or more radio link monitoring configurations in a message from a network node (160).
[3]
The method of Claim 1, wherein obtaining one or more radio link monitoring configurations comprises determining one or more radio link monitoring configurations according to one or more predefined rules.
[4]
The method of any of Claims 1-3, wherein each radio link monitoring configuration comprises: a set of radio resources for performing radio link monitoring within its associated bandwidth portion; and one or more configuration parameters to perform radio link monitoring within its associated bandwidth portion.
[5]
The method of Claim 4, wherein the radio resource set comprises a Channel State Information Reference Signal (CSI-RS) resource.
[6]
The method of Claim 4, wherein the radio resource set comprises a Sync Signal Block (SSB).
[7]
The method of any one of Claims 4-6, wherein the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more of: one or more filter parameters ; one or more radio link failure timers; an evaluation period; a number of retransmissions before the radio link failure is declared; a hypothetical channel configuration; a hypothetical signal configuration; and a mapping function for a measured link quality and a hypothetical channel block error rate.
[8]
The method of Claim 7, wherein: the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more filtering parameters; and the one or more filter parameters comprise one or more of counters N310, N311 and N313, N314.
[9]
The method of any one of Claims 7-8, wherein: the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprises one or more radio link failure timers ; and the one or more radio link failure timers comprise one or more of timers T310, T311, T313 and T314.
[10]
The method of any one of Claims 1-9, wherein at least one of the one or more radio link monitoring configurations obtained comprises a standard radio link monitoring configuration.
[11]
The method of Claim 10, wherein the standard radio link monitoring configuration is associated with a portion of standard bandwidth.
[12]
The method of any one of Claims 1-11, further comprising performing downlink channel quality monitoring of a first part of bandwidth and a second part of bandwidth, the monitoring performance comprising: estimating, during a first period of time, a radio link quality of the first bandwidth portion according to a radio link monitoring configuration associated with the first bandwidth portion; and estimating, over a second period of time, a radio link quality of the second part of bandwidth according to a radio link monitoring configuration associated with the second part of bandwidth, in which the second time period at least partially overlaps with the first period of time.
[13]
The method of Claim 12, wherein: the first bandwidth portion comprises the original bandwidth portion; and the second bandwidth portion comprises the destination bandwidth portion.
[14]
The method of any of Claims 12-13, wherein the monitoring is triggered based on an activation rate of one or more of the first part of bandwidth and the second part of bandwidth.
[15]
The method of any of claims 1-14, wherein the radio link monitoring configuration associated with the destination bandwidth portion comprises a plurality of sets of radio resources and the method further comprises: selecting one or more among the plurality of radio resource sets to be used to perform radio link monitoring in the destination bandwidth portion based on a predefined rule.
[16]
The method of any one of Claims 1-15, wherein a plurality of radio link monitoring configurations are associated with the destination bandwidth portion and the method further comprises: receiving an instruction via control information downlink to use one of the plurality of radio link monitoring configurations to perform radio link monitoring on the destination bandwidth portion.
[17]
17. The method of any of Claims 1-16, wherein a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion use the same radio resources and perform radio link monitoring on the destination bandwidth portion according to the radio link monitoring configuration obtained associated with the destination bandwidth portion comprises: using one or more measures previously performed and samples of measures previously performed to generate out of sync and in sync events.
[18]
The method of any of Claims 1-16, wherein a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion use different radio resources.
[19]
19. The method of Claim 18, wherein performing radio link monitoring on the destination bandwidth portion in accordance with the obtained radio link monitoring configuration associated with the destination bandwidth portion comprises: applying a function of one or more of previously performed measurements and samples of previously performed measurements to generate out of sync and in sync events without resetting a radio link failure timer or radio link failure counter.
[20]
20. The method of Claim 18, wherein performing radio link monitoring on the destination bandwidth portion in accordance with the obtained radio link monitoring configuration associated with the destination bandwidth portion comprises: resetting at least one of a radio link failure timer and a radio link failure counter.
[21]
21. The method of Claim 20, wherein resetting at least one of a radio link failure timer and a radio link failure counter comprises: resetting a set of radio link failure timers and radio frequency counters. radio link failure associated with radio link monitoring for events out of sync; and allow a set of radio link failure timers and radio link failure counters associated with radio link monitoring for synchronous events to continue.
[22]
22. The method of Claim 20, wherein resetting at least one of a radio link failure timer and a radio link failure counter comprises: resetting one or more radio link failure timers without resetting any radio link failure counter.
[23]
23. A method on a network node (160), comprising: determining (901) one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth; configuring (902) a user equipment (UE) (110) to perform radio link monitoring in a destination bandwidth portion according to a radio link monitoring configuration associated with the destination bandwidth portion .
[24]
24. The method of Claim 23, wherein configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion comprises: send an indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE.
[25]
25. The method of Claim 24, wherein sending the indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE comprises:
send an indication of the radio link monitoring configuration associated with the destination bandwidth portion in an information element within a bandwidth portion configuration for the destination bandwidth portion.
[26]
26. The method of Claim 24, wherein sending the indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE comprises: sending an indication of the radio link monitoring configuration associated with the portion of destination bandwidth on an information element within a server cell configuration.
[27]
27. The method of Claim 26, wherein the indication comprises a radio link monitoring configuration identifier.
[28]
28. The method of Claim 23, wherein configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion comprises: configure the UE to determine the radio link monitoring configuration associated with the destination bandwidth portion according to one or more predefined rules.
[29]
29. The method of any of Claims 23-28, wherein each radio link monitoring configuration comprises: a set of radio resources for performing radio link monitoring within its associated bandwidth portion; and one or more configuration parameters to perform radio link monitoring within its associated bandwidth portion.
[30]
30. The method of Claim 29, wherein the radio resource set comprises a Channel State Information Reference Signal (CSI-RS) resource.
[31]
31. The method of Claim 29, wherein the radio resource set comprises a Sync Signal Block (SSB).
[32]
32. The method of any one of Claims 29-31, wherein the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more of: one or more filter parameters ; one or more radio link failure timers; an evaluation period; a number of retransmissions before the radio link failure is declared; a hypothetical channel configuration; a hypothetical signal configuration; and a mapping function for a measured link quality and a hypothetical channel block error rate.
[33]
33. The method of claim 32, wherein: the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more filtering parameters; and the one or more filter parameters comprise one or more of counters N310, N311 and N313, N314.
[34]
34. The method of any one of Claims 32-33, wherein: the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more radio link failure timers ; and the one or more radio link failure timers comprise one or more of timers T310, T311, T313 and T314.
[35]
35. The method of any one of Claims 23-34, wherein at least one of the given one or more radio link monitoring configurations comprises a standard radio link monitoring configuration.
[36]
36. The method of Claim 35, wherein the standard radio link monitoring configuration is associated with a portion of standard bandwidth.
[37]
37. The method of any of Claims 23-36, wherein the radio link monitoring configuration associated with the destination bandwidth portion comprises a plurality of sets of radio resources and the method further comprises: configuring the UE to select one or more from the plurality of radio resource sets to be used to perform radio link monitoring in the destination bandwidth portion based on a predefined rule.
[38]
38. The method of any of Claims 23-37, wherein a plurality of radio link monitoring configurations are associated with the destination bandwidth portion and the method further comprises: sending an instruction to the UE to use a among the plurality of radio link monitoring configurations to perform radio link monitoring in the destination bandwidth portion.
[39]
39. The method of any one of Claims 23-38, wherein a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with a source bandwidth portion destination use the same radio resources, and configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion comprises: configuring the UE to use one or more of previously performed measures and samples of previously performed measures to generate out-of-sync and in-sync events.
[40]
40. The method of any one of Claims 23-38, wherein a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with a source bandwidth portion destination use different radio resources.
[41]
41. The method of Claim 40, wherein configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion comprises: configure the UE to apply a relation function to one or more previously performed measurements and samples of previously performed measurements to generate out-of-sync and in-sync events without resetting a radio link failure timer or radio link failure counter .
[42]
42. The method of Claim 40, wherein configuring the UE to perform radio link monitoring in the destination bandwidth portion according to the radio link monitoring configuration associated with the destination bandwidth portion comprises:
configure the UE to reset at least one of a radio link failure timer and a radio link failure counter.
[43]
43. The method of Claim 42, wherein configuring the UE to reset at least one of a radio link failure timer and a radio link failure counter comprises: configuring the UE to reset a set of radio link failure timers radio link and radio link failure counters associated with radio link monitoring for events out of sync; and configuring the UE to allow a set of radio link failure timers and radio link failure counters associated with radio link monitoring for synchronous measurements to continue.
[44]
44. The method of Claim 42, wherein configuring the UE to reset at least one of a radio link failure timer and a radio link failure counter comprises: configuring the UE to reset one or more radio link failure timers radio link without resetting any radio link failure counter.
[45]
45. A user equipment (UE) (110), comprising: a receiver (114, 122); a transmitter (114, 122); and processing circuitry (120) coupled to the receiver and transmitter, the processing circuitry configured to: obtain (701) one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth; determining (702) that the UE should switch from a source bandwidth portion to a destination bandwidth portion; and performing (703) the radio link monitoring in the destination bandwidth part, according to a obtained radio link monitoring configuration associated with the destination bandwidth part.
[46]
46. The UE of Claim 45, wherein the processing circuitry configured to obtain one or more radio link monitoring configurations is additionally configured to receive one or more radio link monitoring configurations in a message to from a network node (160).
[47]
47. The UE of claim 45, wherein the processing circuitry configured to obtain one or more radio link monitoring configurations is further configured to determine one or more radio link monitoring configurations according to a or more predefined rules.
[48]
48. The UE of any of Claims 45-47, wherein each radio link monitoring configuration comprises: a set of radio resources for performing radio link monitoring within its associated bandwidth portion; and one or more configuration parameters to perform radio link monitoring within its associated bandwidth portion.
[49]
49. The UE of Claim 48, wherein the radio resource set comprises a Channel State Information Reference Signal (CSI-RS) resource.
[50]
50. The UE of Claim 48, wherein the radio resource set comprises a Sync Signal Block (SSB).
[51]
51. The UE of any of Claims 48-50, wherein the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more of: one or more filter parameters ; one or more radio link failure timers; an evaluation period; a number of retransmissions before the radio link failure is declared; a hypothetical channel configuration; a hypothetical signal configuration; and a mapping function for a measured link quality and a hypothetical channel block error rate.
[52]
52. The UE of Claim 51, wherein: the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more filtering parameters; and the one or more filter parameters comprise one or more of counters N310, N311 and N313, N314.
[53]
53. The UE of any of Claims 51-52, wherein: the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more radio link failure timers ; and the one or more radio link failure timers comprise one or more of timers T310, T311, T313 and T314.
[54]
54. The UE of any one of Claims 45-53, wherein at least one of the one or more radio link monitoring configurations obtained comprises a standard radio link monitoring configuration.
[55]
55. The UE of Claim 54, wherein the standard radio link monitoring configuration is associated with a portion of standard bandwidth.
[56]
56. The UE of any one of Claims 45-55, wherein the processing circuitry is further configured to perform a downlink channel quality monitoring of a first part of bandwidth and a second part of bandwidth. band, the set of processing circuits configured to perform monitoring additionally configured to: estimate, during a first period of time, a radio link quality of the first part of bandwidth according to an associated radio link monitoring configuration the first part of bandwidth; and estimating, over a second period of time, a radio link quality of the second part of bandwidth according to a radio link monitoring configuration associated with the second part of bandwidth, in which the second time period at least partially overlaps with the first period of time.
[57]
57. The UE of Claim 56, wherein: the first bandwidth portion comprises the original bandwidth portion; and the second bandwidth portion comprises the destination bandwidth portion.
[58]
58. The UE of any one of Claims 56-57, wherein the processing circuitry is further configured to trigger monitoring based on an activation rate of one or more of the first part of the bandwidth and the second part of bandwidth.
[59]
59. The UE of any of Claims 45-58, wherein the radio link monitoring configuration associated with the destination bandwidth portion comprises a plurality of radio resource sets and the processing circuitry is configured additionally to: select one or more from the plurality of sets of radio resources to be used to perform radio link monitoring in the destination bandwidth portion based on a predefined rule.
[60]
60. The UE of any of Claims 45-59, wherein a plurality of radio link monitoring configurations are associated with the destination bandwidth portion and the processing circuitry is further configured to: receive an instruction through downlink control information to use one of the plurality of radio link monitoring configurations to perform radio link monitoring in the destination bandwidth portion.
[61]
61. The UE of any of Claims 45-60, wherein a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion use the same radio resources and the processing circuitry configured to perform radio link monitoring on the destination bandwidth portion according to the radio link monitoring configuration obtained associated with the destination bandwidth portion it is additionally configured to: use one or more of previously performed measurements and samples of previously performed measurements to generate out of sync and in sync events.
[62]
62. The UE of any of Claims 45-60, wherein a radio link monitoring configuration associated with the source bandwidth portion and the radio link monitoring configuration associated with the destination bandwidth portion use different radio resources.
[63]
63. The UE of Claim 62, wherein the processing circuitry configured to perform radio link monitoring in the destination bandwidth portion according to the obtained radio link monitoring configuration associated with the destination band is additionally configured to: apply a relation function to one or more of previously performed measurements and samples of previously performed measurements to generate out-of-sync and in-sync events without resetting a radio link failure timer or timer. radio link failure.
[64]
64. The UE of Claim 62, wherein the processing circuitry configured to perform radio link monitoring on the destination bandwidth portion according to the obtained radio link monitoring configuration associated with the destination band is additionally configured to: reset at least one of a radio link failure timer and a radio link failure counter.
[65]
65. The UE of Claim 64, wherein the processing circuitry configured to reset at least one of a radio link failure timer and a radio link failure counter is further configured to:
redefine a set of radio link failure timers and radio link failure counters associated with radio link monitoring for out of sync events; and allow a set of radio link failure timers and radio link failure counters associated with radio link monitoring for synchronous events to continue.
[66]
66. The UE of Claim 62, wherein the processing circuitry configured to reset at least one of a radio link failure timer and a radio link failure counter is further configured to: reset one or more timers link failure without resetting any radio link failure counter.
[67]
67. A network node (160), comprising: a receiver (190, 172); a transmitter (190, 172); and set of processing circuits (170) coupled to the receiver and transmitter, the set of processing circuits configured to: determine (901) one or more radio link monitoring configurations, each radio link monitoring configuration associated with at least a portion of bandwidth; configuring (902) a user equipment (UE) (110) to perform radio link monitoring in a destination bandwidth portion according to a radio link monitoring configuration associated with the destination bandwidth portion .
[68]
68. The network node of Claim 67, wherein the processing circuitry configured to configure the UE to perform radio link monitoring in the destination bandwidth portion according to the associated radio link monitoring configuration the destination bandwidth portion is additionally configured to: send an indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE.
[69]
69. The network node of Claim 68, wherein the processing circuitry configured to send the indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE is further configured to: send a indication of the radio link monitoring configuration associated with the destination bandwidth portion in an information element within a bandwidth portion configuration for the destination bandwidth portion.
[70]
70. The network node of Claim 68, wherein the processing circuitry configured to send the indication of the radio link monitoring configuration associated with the destination bandwidth portion to the UE is further configured to: send a indication of the radio link monitoring configuration associated with the destination bandwidth portion of an information element within a server cell configuration.
[71]
71. The network node of Claim 70, wherein the indication comprises a radio link monitoring configuration identifier.
[72]
72. The network node of Claim 67, wherein the processing circuitry configured to configure the UE to perform radio link monitoring in the destination bandwidth portion according to the associated radio link monitoring configuration the destination bandwidth portion is additionally configured to: configure the UE to determine the radio link monitoring configuration associated with the destination bandwidth portion according to one or more predefined rules.
[73]
73. The network node of any of Claims 67-72, wherein each radio link monitoring configuration comprises: a set of radio resources for performing radio link monitoring within its associated bandwidth portion; and one or more configuration parameters to perform radio link monitoring within its associated bandwidth portion.
[74]
74. The network node of Claim 73, wherein the radio resource set comprises a Channel State Information Reference Signal (CSI-RS) resource.
[75]
75. The network node of Claim 73, wherein the radio resource set comprises a Sync Signal Block (SSB).
[76]
76. The network node of any one of Claims 73-75, wherein the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more of: one or more parameters filtering; one or more radio link failure timers; an evaluation period; a number of retransmissions before the radio link failure is declared; a hypothetical channel configuration; a hypothetical signal configuration; and a mapping function for a measured link quality and a hypothetical channel block error rate.
[77]
77. The network node of Claim 76, wherein: the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more filtering parameters; and the one or more filter parameters comprise one or more of counters N310, N311 and N313, N314.
[78]
78. The network node of any of Claims 76-77, wherein: the one or more configuration parameters for performing radio link monitoring within its associated bandwidth portion comprise one or more link failure timers radio; and the one or more radio link failure timers comprise one or more of timers T310, T311, T313 and T314.
[79]
79. The network node of any of Claims 67-78, wherein at least one of the one or more determined radio link monitoring configurations comprises a standard radio link monitoring configuration.
[80]
80. The network node of Claim 79, wherein the standard radio link monitoring configuration is associated with a portion of standard bandwidth.
[81]
81. The network node of any of Claims 67-80, wherein the radio link monitoring configuration associated with the destination bandwidth portion comprises a plurality of sets of radio resources and the set of processing circuits it is additionally configured to: configure the UE to select one or more from the plurality of sets of radio resources to be used to perform radio link monitoring in the destination bandwidth portion based on a predefined rule.
[82]
82. The network node of any of Claims 67-87, wherein a plurality of radio link monitoring configurations are associated with the destination bandwidth portion and the processing circuitry is further configured to: send an instruction for the UE to use one of the plurality of radio link monitoring configurations to perform radio link monitoring on the destination bandwidth portion.
[83]
83. The network node of any of Claims 67-82, wherein a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with the destination band uses the same radio resources and processing circuitry configured to configure the UE to perform radio link monitoring on the destination bandwidth portion according to the radio link monitoring configuration associated with the portion destination bandwidth is additionally configured to: configure the UE to use one or more of previously performed measurements and samples of previously performed measurements to generate out-of-sync and in-sync events.
[84]
84. The network node of any one of Claims 67-82, wherein a radio link monitoring configuration associated with a source bandwidth portion and the radio link monitoring configuration associated with the destination band uses different radio resources.
[85]
85. The network node of Claim 84, wherein the processing circuitry configured to configure the UE to perform radio link monitoring in the destination bandwidth portion according to the associated radio link monitoring configuration the destination bandwidth portion is additionally configured to: configure the UE to apply a relation function to one or more previously performed measures and samples of previously performed measures to generate out-of-sync and in-sync events without resetting a fault timer link link or a radio link failure counter.
[86]
86. The network node of Claim 84, wherein the processing circuitry configured to configure the UE to perform radio link monitoring in the destination bandwidth portion according to the associated radio link monitoring configuration the destination bandwidth portion is additionally configured to: configure the UE to reset at least one of a radio link failure timer and a radio link failure counter.
[87]
87. The network node of Claim 86, wherein the processing circuitry configured to configure the UE to reset at least one of a radio link failure timer and a radio link failure counter is additionally configured to : configure the UE to reset a set of radio link failure timers and radio link failure counters associated with radio link monitoring for out of sync events; and configuring the UE to allow a set of radio link failure timers and radio link failure counters associated with radio link monitoring for synchronous measurements to continue.
[88]
88. The network node of Claim 86, wherein the processing circuitry configured to configure the UE to reset at least one of a radio link failure timer and a radio link failure counter is additionally configured to : configure the UE to reset one or more radio link failure timers without resetting any radio link failure counter.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020009644A2|2020-11-10|reconfiguration of radio link monitoring / radio link failure by switching parts of bandwidth

---

US20210337615A1|2021-10-28|Flexible resume and reconfigurations in multi-radio dual connectivity and standalone scenarios

---

BR112020017498A2|2020-12-22|METHODS PERFORMED BY A USER EQUIPMENT AND A NETWORK NODE, USER EQUIPMENT, AND, NETWORK NODE

---

BR112020009554A2|2020-11-03|complete rrc configuration in en-dc

---

US20220014953A1|2022-01-13|Measurement Configuration in NR-DC

---

BR112020016542A2|2021-03-02|methods performed by a wireless device and a base station to perform a random access procedure, wireless device method, wireless device, and, base station.

---

BR112020010800A2|2020-11-10|measurement report configuration to help classify beam / cell level measurements

---

WO2019194716A1|2019-10-10|Performing cell measurements

---

US20210266932A1|2021-08-26|Methods, Apparatus and Computer-Readable Media Related to Semi-Persistent Scheduling Configuration

---

IL282207D0|2021-05-31|Mobility procedure and wireless device for performing said procedure

---

WO2021034254A1|2021-02-25|Updating a pci in a du-cu split architecture

---

US20210243624A1|2021-08-05|Measurement Reporting Timer

---

US20210227409A1|2021-07-22|Methods of Controlling Adaptive UE Beam Measurement Capability

---

CN113615247A|2021-11-05|Conditional mobility triggering based on beam information

---

US11026204B2|2021-06-01|Methods providing release and re-direct message contents and UE behavior and related wireless devices

---

WO2022031208A1|2022-02-10|Configuring and/or detecting measurement report triggering events based on unbalanced reference signals and related communication devices and network nodes

---

BR112021008138A2|2021-08-03|methods performed by a wireless device and a first and second network nodes, wireless device, and, first and second network nodes

---

WO2019194725A1|2019-10-10|Performing cell measurements

---

WO2021206602A1|2021-10-14|Configuration and/or reporting of measurements in logged mdt

---

WO2021162605A1|2021-08-19|Synchronization and random access during connection resume

---

WO2022031212A1|2022-02-10|Transferring events related to beam measurements

---

WO2021242167A1|2021-12-02|Reconnection cell id in rlf report

---

WO2021130639A1|2021-07-01|Filtering relevant early measurement results

---

WO2020167187A1|2020-08-20|Enhancements to mdt

同族专利:

---

公开号 | 公开日

---

RU2745448C1|2021-03-25|

---

TWI712277B|2020-12-01|

---

TW201924251A|2019-06-16|

---

US20200344019A1|2020-10-29|

---

CN111345058A|2020-06-26|

---

WO2019097432A1|2019-05-23|

---

KR20200069355A|2020-06-16|

---

JP2021503754A|2021-02-12|

---

KR20220016282A|2022-02-08|

---

EP3711341A1|2020-09-23|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US8995366B2|2012-03-23|2015-03-31|Google Technology Holdings LLC|Radio link monitoring in a wireless communication device for a enhanced control channel|

---

US8976698B2|2012-08-09|2015-03-10|Qualcomm Incorporated|Methods and apparatus for radio link monitoring in new carrier type in a long term evolution system|

---

US9173109B2|2013-03-15|2015-10-27|Blackberry Limited|Radio link quality monitoring|

---

CN104469945B|2013-09-12|2019-01-25|索尼公司|Activated control and method, the management method and base station apparatus of NCT SCC|

---

ES2802098T3|2014-01-27|2021-01-15|Ericsson Telefon Ab L M|Methods and user equipment for adaptive radio link monitoring|CN109644362B|2018-02-05|2021-02-23|Oppo广东移动通信有限公司|Method for detecting link quality and terminal equipment|

---

SG11202009465TA|2018-03-29|2020-10-29|Beijing Xiaomi Mobile Software Co Ltd|Information reporting method and apparatus, and bandwidth part based operating method and apparatus|

---

SG11202010700YA|2018-05-07|2020-11-27|Guangdong Oppo Mobile Telecommunications Corp Ltd|Method and apparatus for suspending rrc connection, and computer storage medium|

---

US11140722B2|2018-11-01|2021-10-05|Ofinno, Llc|Pathloss measurement in multiple cells|

---

US11228976B2|2019-02-15|2022-01-18|Mediatek Inc.|Power saving for new radio carrier aggregation|

---

CN112351500A|2019-08-09|2021-02-09|大唐移动通信设备有限公司|BWP group switching method, base station and terminal|

---

WO2021134792A1|2020-01-03|2021-07-08|华为技术有限公司|Method and apparatus for determining evaluation duration during downlink transmission quality inspection|

---

US20210306059A1|2020-03-25|2021-09-30|Qualcomm Incorporated|Radio link monitoring across multiple frequencies in wireless communications|

---

CN113543037A|2020-04-14|2021-10-22|华为技术有限公司|Communication method and device|

---

WO2021226836A1|2020-05-12|2021-11-18|LenovoLimited|Method and apparatus for an enhanced failure report mechanism for mcg and scg|

---

WO2021229136A1|2020-05-13|2021-11-18|Nokia Technologies Oy|Prolonging voice service in an active state|

---

WO2021237669A1|2020-05-29|2021-12-02|Apple Inc.|Bandwidth part switching in 5g new radio dual connectivity|

---

US20220038933A1|2020-08-03|2022-02-03|Qualcomm Incorporated|Techniques for determining beam failure or radio link failure|

---

WO2022027693A1|2020-08-07|2022-02-10|华为技术有限公司|Communication method and apparatus|

---

WO2022036706A1|2020-08-21|2022-02-24|华为技术有限公司|Communication method and communication apparatus|

---

CN112714481B|2021-03-26|2021-07-02|新华三技术有限公司|BWP switching method and base station equipment|

法律状态:
2021-12-07| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762587360P| true| 2017-11-16|2017-11-16|

---

US62/587,360|2017-11-16|

---

PCT/IB2018/058975|WO2019097432A1|2017-11-16|2018-11-14|Radio link monitoring/radio link failure re-configuration upon bandwidth parts switching|

---